Register for Visual Studio 2010 Beta Exams (.NET 4.0)

Time for (free) Beta Exams again

Information can be found from here

http://blogs.technet.com/betaexams/archive/2010/03/17/register-for-tools-utilities-2010-beta-exams.aspx

Register via http://register.prometric.com

For easier reference, exams available are listed below (along with PromoCode)

Exam 71-511, TS: Windows Applications Development with Microsoft .NET Framework 4 – 511BC

Exam 71-515, TS: Web Applications Development with Microsoft .NET Framework 4 – 515AA

Exam 70-513: TS: Windows Communication Foundation Development with Microsoft .NET Framework 4 – 513CD

Exam 70-516: TS: Accessing Data with Microsoft .NET Framework 4 – 516B1

Exam 70-518: Pro: Designing and Developing Windows Applications Using Microsoft .NET Framework 4 – 518PE

Exam 70-519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4 – 519ZS

And as always, word of advice, read and master the items in prep guide to increase your chances of passing the exams.

Good luck!

Safety settings on this machine prohibit accessing a data source on another domain

Encountered this message many times with sites using PivotTable component of OWC11 (office web components) “Safety settings on this machine prohibit accessing a data source on another domain

This is a browser restriction (at least with IE). Before resolving this, make sure you are accessing a trusted site.

Resolution:

1. Add site to the zone (e.g. it is recommended that you only allow your trusted sites to be exempted from this restriction). So add the site (if you trust it) to your Trusted Zone. Internet Options > Security

2. Modify Security Level of that Zone (e.g. Trusted Zone). Custom Level button. A pop-up dialog should appear. Go the Miscellaneous Settings section. Then you should be a setting for “Access data sources across domains”. Recommended to set it to Prompt. If that option is selected you will be prompted when a component requires this permission.

Hope that helps.

Windows XP Service Pack 3 Now Available

I just received a notification of Service Pack 3 for Windows XP availability when I opened my PC. (automatic updates – have mine set to notify when updates are available)

Here a link to Release Notes which I recommend reading before installing the update. [more]

In the release notes it says:

Internet Explorer

If you have installed Windows Internet Explorer® 7 or a beta version of
Internet Explorer 8, and then install Windows XP SP3, you cannot uninstall
Internet Explorer.

To avoid this, ensure Internet Explorer 7 or a beta version of Internet
Explorer 8 is not installed before installing Windows XP SP3.

If you have already encountered this issue, uninstall Windows XP SP3,
uninstall Internet Explorer, and then reinstall Windows XP SP3.

Looks clear enough but will see and update with additional information I can find. 

Install .NET Windows Service with Visual Studio Setup Wizard or Project

I've done this a couple of times but I still tend to forget at times so
I might as well post here for me and hopefully someone else's reference.

To create a Windows Service see this article by Ken Getz : Windows Services: New Base Classes in .NET Make Writing a Windows Service Easy

There
are a number of ways to install a windows service, one of which is
using installutil.exe but this post will be using Setup Project which
for me is a little easier to implement: [more]

Was working with VS2005 for this but I think the same things with VS2003 and will update this one for VS2008 soon.

Using SetUp Wizard template
1) open your Windows Service project in VS
2) add a Setup project to your solution

  • File > Add Project > New Project > Setup and Deployment Projects > Setup wizard
  • Set the location appropriate for your situation and click on OK

3) in the Setup wizard, skip page 1.
4) On page 2 (of 5) select "Create a Setup for a Windows application."
5) On page 3, select "Primary output from ."
6) On page 4, click on Finish.
7) The final step (a crucial one) is to add a custom action to run the code in the installer class you added to your project.

  • Right click on the setup project (Solution Explorer)
  • View > Editor > Custom Actions.
  • Right-click on the Install node in the Custom Actions treeview.
  • In the Select Item in Project dialog, make sure Application Folder is selected, and click on OK.
  • Click on OK again to select the "Primary output from " option. You should now see this as a child node of the Install node.

That's
all you have to do. Rebuild both the project and the setup project, run
the installation, and the service should be installed as a Windows
service.

Of course, this scenario doesn't deal with getting the
service started. Even if you've set the ServiceInstaller component's
StartType property to Automatic, you have to reboot the computer to
start the service. (Or, you can use the services.msc applet and start
it yourself.)


——–
Another alternative is to use the Setup Project instead of Setup Wizard.
1) Same as step 1 above
2) add a Setup project to your solution

  • file > Add Project > New Project > Setup and Deployment Projects > Setup Project (rather than Setup Wizard as above)
  • set the location appropriate for your situation and click on OK

3) Right click on the Setup Project (in Solution Explorer)

  • Add > Project Output > Select your Windows Service in the Project dropdown
  • Select Primary Output in the list below it.
  • Click OK

4) The final step (a crucial one) is to add a custom action to run the code in the installer class you added to your project.

  • Right click on the setup project (Solution Explorer)
  • View > Editor > Custom Actions.
  • Right-click on the Install node in the Custom Actions treeview.
  • In the Select Item in Project dialog, make sure Application Folder is selected, and click on OK.
  • Click on OK again to select the "Primary output from " option. You should now see this as a child node of the Install node.

Basically the difference is how the Output was specified to include the "Primary output from .".

Assuming there's nothing wrong with your VS, .NET framework then this should be easy.