Using Powershell script to start and stop web services during development

I have been developing some Web Services under VS2008 and Vista 64.

For some reason whenever I tried to test the services under VS2008 I received the message :

Unable to launch the ASP,NET Development Server because port XXXX is in use.

I decided to start and stop the services manually using Powershell and, if debugging was required to used the "Debug->Attach to Process" facility.

Here is the Powershell command to start an instance of the development server on a specified port:

&"C:\Program Files (x86)\Common Files\microsoft shared\DevServer\9.0\WebDev.WebServer.EXE" /port:1420 /path:"C:\Users\User Name\Documents\Code\Services\Status"

Here is the Powershell command to stop all instances of the development server:

&stop-process -name WebDev.WebServer -confirm

Regards

Andy

ClickOnce - Manually modifying the Application file list.

I am developing a ClickOnce application which requires assemblies and other resources which are not automatically included in the "Application Files".

You can include files in the "Applciation Files" list by adding them to the project. (i.e In VS rightclick on the ClickOnce project and select Add->Existing Item.

The problem with this is that the files are copies into the Project directory.

A better way to handle this is to use an Xml editor to manually edit the project file (*.csproj).

Refer to blogs.msdn.com/mwade/archive/2008/06/29/how-to-publish-files-which-are-not-in-the-project

Regards

Andy

Install Opera Code Signing Certificates into Vista

I recently purchased a "code signing" certificate from Comodo . Comodo charge about half as much as Thawte who are about half of Verisign.
The certificate transfer process is pretty tricky and the certificate ends up installed in the Certificate store of the browser used to request and transfer it.
YOU MUST USE THE SAME BROWSER TO ORDER AND DOWNLOAD THE CERTIFICATE.
I recommend using Opera 9.6 to order and download certificates.
Because I had difficulties with the ordering and download process Comodo issued a replacement certificate. Unfortunately I then used the first certificate for code signing. Comodo had revoked this certificate and the ClickOnce install dialog indicated "Unknown Publish". However, there was NO indication in the Windows Certificate Manager "CertMrg.msc" that the certifcate had been revoked. This issue was only resolved when Comodo support told me the serial number of working certificate.


To install the certificate in Vista proceed as follows:

First export the certificate from the browser ( In this case Opera 9.63 ).

Tools->Preferences->Advanced Tab.
You should see a "Manage Certificates" button.
Press the button.
The browser certificate manager will be displayed. The downloaded code signing certificates should be shown under the "Personal" tab.

Select the certificate and press the "Export" button on the right side of the form.

A file create dialog is displayed. Give the exported certificate a file name and select to save as type "PKCS #12 (*.p12) This type is equivalent to the Windows .pfx type.

Follow the dialogs to export the certificate.


Now install the certificate into the Vista certificate store.

First run the Vista Certificate manage program "certmgr.msc"

Select the Personal/Certificates folder and then Ations->All Tasks->Import

Select the file exported above ( be sure to filter on file type .p12 ).

Follow the import wizard. Be sure NOT to select the

"Enable strong private key protecion" VS Code signing cannot handle the password request

Place the certicate in the "Personal" folder.

The certificate should now be availabe for code signing in VS.

Good luck. Andy

Microsoft StyleCop - Editing setting under Vista 64

Microsoft StyleCopy 4.3 has a master settings file named Settings.StyleCop
This file may be edited with the StyleCopSettingsEditor.exe.
Under Vista 64 write access to the program folders is restricted to users with Administrator privileges.
Here's the rub.
StyleCopSettingsEditor must be running as Administrator to write setting changes to
Settings.StyleCop.
Settings.StyleCop is associated with StyleCopSettingsEditor.exe thru the StyleCop extension, but the "Run as Administrator" option is only available when clicking on exe's.
You can "Run as Administrator" StyleCopSettingsEditor.exe but the exe requires a command line parameter pointing to Settings.StyleCop.

The solution:
Create a shortcut on the desktop to StyleCopSettingsEditor.exe.

Append "Settings.StyleCop" to the target which becomes:

"C:\Program Files (x86)\Microsoft StyleCop 4.3\StyleCopSettingsEditor.exe" "Settings.StyleCop"

Under the Compatibility tab check "Run as Administrator"

Double Click the shortcut to launch StyleCopSettingsEditor.exe. The program is now running as Administrator and has sufficient rights to update Settings.StyleCop in the program folder.