You know, I just shake my head at this configuration environment approach to software development as I try and rework the CardSpace examples for the new June CTP. It feels like being back at square one again.

First there was C, just a coloured text editor. Then we eventually progressed to rich, Intellisense-based, context-sensitive-help development. Then web development was introduced and we were back to coloured text editors again. Finally we again progressed to rich, Intellisense-based, context-sensitive-help development. Now comes factories, SOA, and XML-based development. Now we are back to coloured text editors again.

I feel historically Microsoft builds highly productive development enironments. So I think there are three things Microsoft needs to do with the release of .NET 3.0 to not leave us in the dark ages of coloured text editors (oxymoron?) again.

1) More robust Intellisense in XML files. It still seems flakey to me and this is already the third version of the Visual Studio .NET-based development editor. In fact, maybe it's time they bought XML-SPY because quite frankly their XSL and XSD editors blow too. I know this is a bit of an aside but it just ticks me off that I have to spend thousands on VS and then another $500 - $1000 on XML-SPY for maximum productivity.

2) Xml object browser equivalent to the class browser. It is a massive time-waster sifting through the MSDN class model looking for xxxElement classes trying to piece together the structure of the Xml on ever increasing complex SOA schemas.

3) Context-sensitive help in the XML editors. I should not hit F1 on <system.serviceModel> and get the MSDN for "configuration Element (General Settings Schema)"

I hear your frustration! But don't worry, it's not as bad as it seems. The fact is that when Garrett and I build our CardSpace samples we tend to do it using raw XML in notepad or some other text/code editor. This is chiefly because we're living on the bleeding edge with daily builds and the nice UI tools lag behind somewhat.

The reality is that there are some very good tools to make developers' lives easier. Look at http://msdn.microsoft.com/windowsvista/downloads/products/getthebeta/default.aspx#developWinFXApps

Steps 3 and 4 provide what you need. The Windows SDK not only contains sample code, it also contains the WCF Configuration Editor, SvcConfigEditor.exe, which provides you with a nice UI for editing config files and insulates you from the raw XML. The "Orcas" .NET Framework 3.0 Development Tools provides the Intellisense support and documentation integration you're after.

My apologies if you're already aware of these tools and are still unhappy. If so, please keep giving the feedback. Here is a link to the main beta feedback links and also this is a good place for feedback specifically on CardSpace and the CardSpace community site. Your feedback gets read and acted upon by people in the Product Groups.

We're not deliberately trying to make life hard! We want to make our tools and technology as useful and productive as possible but by their very nature the tools come later than the code.

-Nigel

Ah, right, the Orca Tools. I forgot about that install amongst trying to piece together all of the pieces for the June CTP. I'll have to look at the other exe's in the Windows SDK too, thanks. [edit] I just tried and enjoyed the service config editor. It is a much more robust and slick version of the application blocks config editor. bravo. As well, step 4 for the Orca install seems to point to a May 23 .msi that is incompatible with JuneCTP. No biggee. [edit]

As for the XML Editor I'll definately checkout the main feedback site and Orca. It's something that has bothered me since day one as you saw in my post. I thought by version three of VS it would be up to par with the VB/C# editor. Maybe in Orca. Anyway... a story for the feedback site :)

I've been using the Windows SDK 6.0 along with the JuneCTP since I downloaded it. Please correct me if I am wrong (seriously, please do!), but I was unable to find any CardSpace samples in the WCFSamples.zip TechnologySamples folders or any of the other sample zip files. My focus is doing a proof of concept for us being an Identity Provider.

I need the equivalent of the SecurityTokenServiceSamples folder from the FederatedIdentityAndAccessResourceKitSept2005CTP.msi that works with JuneCTP. I've spent the last week trying to convert the samples here to work with JuneCTP. I finally got to a point where I am totally stuck and was going to post the problem when the alert for this post came in. In the mean time, I'll post my problem while I wait to here back to you on the location of the CardSpace samples in the Windows SDK 6.0.

Thanks Nigel, I appreciate all the work you guys are doing!