Martin Hinshelwood's ALM Blog

A Scottish software developer: SSW Solution Architect, Microsoft Visual Studio ALM MVP & Scrum Developer Trainer

  Home  |   Contact  |   Syndication    |   Login
  410 Posts | 10 Stories | 576 Comments | 57 Trackbacks

News

www.SSW.com.auSSW was the first company in the world outside of Microsoft to deploy Visual Studio 2010 Team Foundation Server to production, not once, but twice.

Team Foundation Server

Visual Studi2010 ALM SSW provides expert Visual Studio ALM guidance including installation, configuration and customisation through our four Microsoft Visual Studio ALM MVP’s in three countries; Australia, Beijing and the UK. They have experience deploying to small development shops all the way through to large blue chips.

Call us on +(44) 141 416 0993 or +(61) 2 9953 3000 to get started!

Professional Scrum Developer Training

Professional Scrum Developer Training SSW has six Professional Scrum Developer Trainers who specialise in training your developers in implementing Scrum with Microsoft's Visual Studio ALM tools.

Call us on +(44) 141 416 0993 or +(61) 2 9953 3000 to get started!

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Personal








Locations of visitors to this page

Twitter












Tag Cloud


Article Categories

Archives

Post Categories

Image Galleries

Blogs I read

Blogs of Friends

Personal

Projects

VSTS

Absolutely brilliant. That's what I think of Linq to XSD. Disappointed that is only works in C#, but having to use C# for a single project out of a solution it is a small price to pay to get the functionality.

If you install the LINQ to XSD Preview Alpha 0.2 Refresh you get a couple of extra project definitions:

image

If you create one of these it will have the features enabled. You can add the features to an existing project by editing the project definition file to add a property group:

   1: <PropertyGroup>
   2:   <TXLINQBinDir Condition="'$(TXLINQBinDir)' == ''">$(ProgramFiles)\LINQ to XSD Preview\Bin</TXLINQBinDir>
   3: </PropertyGroup>

And an import reference:

   1: <Import Project="$(TXLINQBinDir)\LinqToXsd.targets" />

note: if you are using MSBuild or Team Build you will need to install this add on there as well....

Now that you have a project, when you add an XSD you will have extra Build Actions available. Once you have set all of your XSD files to this Action and build, you will have classes for all of your XSD's. On down side is that it created a single file ("/obj/debug/LinqToXsdSource.cs"), bit it does work.

Technorati Tags: ,,
posted on Thursday, August 28, 2008 2:48 PM

Feedback

# re: LINQ to XSD 4/16/2009 12:40 AM Marco Mangia
hi martin,
i followed your instructions to add the features to an existing project. Mine is web asp.net MVC project, where xml file and xsd schema are placed in AppData folder. But when compiling no class is generated. :-(
would u know where i am wrong?

Marco Mangia

Comments have been closed on this topic.