Andrew MacNeill - AKSEL Solutions

I've been working on a few ASP.Net projects and one of the key aspects of this project is creating some usable XSD schemas that are then translated into objects. At first, I started using the regular xsd.exe that creates a class (in either VB or C#) from a schema with the simple statement. xsd "myfile.xsd" /l:CS /o:"C:\MyOutput\" /c But I always wanted to have this directly within Visual Studio. I'm sure there's another way (so please let me know) but then I found Xsd2Code .net class generator3.0 . It does the same thing that XSD does but also lets you create add Serialize and DeSerialize options, making it easier to convert a basic XML file into an object. var o = FormInstance.Deserialize(xml); The best part is that it's a Visual Studio plug-in (from Codeplex of course), so you can right-click on an XSD file and have it generate the necessary code. By default, the Serialization methods aren't included - but it's an option right from the gen...

Rick had posted two weeks ago about how some VFP updates were coming down the Microsoft pipe. They were released recently but unfortunately, have some glitches. Shedding Some Light - Comment I typically use the VFP online help or rely on other sources but it might be nice if the entire help file could be "codeplexed". That way, the Fox team doesn't have to pull their resources from all over to get it done and community members could get it cleaned up. Just a thought.  

Many developers who want to get involved with VFPX face a bit of a challenge, especially if they've never used Source Control. (What!?!?! You've never used source control) When I started working on the Code Analyst, I used the SCCI provider within VFP but it always conflicted with my own SSC tool (SourceOffSite). There's also a TeamPrise Explorer or one built directly into Visual Studio but within VFP, I wanted something a little more, um, basic. So there's a CodePlex SC command line click, that's really easy to work with.  I'm still experimenting with it - but in the end, I think it may be the way to go. One thing to realize though is that it will give you FULL access to the VFPX project, which includes LOTS of sub-projects. I only wanted to work on the Code Analyst but as a result, I ended up getting everything. I don't think that's a bad thing because it makes it easier to really appreciate the entire scope of the VFPX project. After all, this IS the...