Visual Studio

xsd.exe location (Windows 7, VS2010)

Today I had to generate an xsd (xml schema file) from an existing xml file.

In the past, I had used xsd.exe, which lived in the SDK directory of VS2008.

As I do not have VS2008 installed on my current machine, I had to go hunting for it. On a Windows 7 machine running VS2010, xsd.exe should be found in:

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin

or

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\x64

You can then run this application from the command prompt in order to generate an xsd file, as per the usage instructions on msdn here.

Et Voila!

xsd.exe outout
xsd.exe outout
Visual Studio

Converting a Website to a Web Application in Visual Studio 2010

[youtube http://www.youtube.com/watch?v=oXptokM0v7w]

 

I personally will always chose to create a browser facing web based product as a Web Application in Visual Studio 2010. The main reason being that Web Applications actually create a project file containing all of the configuration details for your application. The other being that you don’t need to set anything up in IIS on your local machine.

I recently inherited a Web Site that needed some changes. It was an asp.net site, and the first thing I did was to convert it to a Web Application, just to at least get that explicit definition of what was in the project from the Project file.

It also makes debugging easier if you need to debug your site from the root of your localhost – IIS Express and Cassini will just run a Web Application on a specific port from the root. Web Sites however will run from a Virtual Directory (e.g. http://localhost/MyWebSite/). Web Sites can be configured to run under a port, but it isn’t a simple process.

And of course the other advantage of having a Project file containing all of your Web Server configuration for debugging is actually stored within a file, that can be kept under source control, and can be shared with others without the need for lengthy debugging instructions.