that component-cd is your framework
i guess, something went wrong while installing...

uninstall that SDK framework  and VS.NET (if already installed  a part) firstly
then start with installing the components...

sideline: don't forget to install  IIS first on your PC and make sure it runs
while installing VS.NET

Well, uninstall your framework  then, saving your framework samples incase you
have been playing with them.

I did that once (before my total reinstall) except I put  the framework on top of
VS.NET ... worked fine.
The installs are identical as far as I can tell.

Maybe some components  are updated in one or the other, just patch up whatver you
end up with.

Make sure when you do install  VS.NET then copy your samples straight on top of
them.

I would just go ahead and slam it on top - I think it'll be ok. But save your
samples first else changes will be overwritten.

Make sure you specify the same directories you currently have ... i.e. for
samles and sqlserver etc. It should be alright.

I had not used any thing.... I was straight installing a new machine. First
I installed  SQL Server Developer Edition, patched it with SP 3, then
installed IIS, made sure it was running, then installed .NET Framework, ran
the installation programs for the MSDE instance and samples/tutorials,
verified they were working and I could get to all the different samples,
tutorials etc, patched the MSDE instance with the special SP3 for it, then
patched .NET framework  with SP 1. That is the point I was at when I was
going to install  VS.NET and got the windows  Component Update saying I needed
.NET Framework and the other two things.

I read the installation notes for the windows component  upgrade and manually
installed the runtime  files and the Front Page Web extensions client. I
then started install again and verified that the windows component upgrade
only said it needed .NET Framework. Using the information from the read me
I restarted the installation from the command line using the NO_BSLN_CHECK
option. When I got to the screen where it lists the options to install I
unchecked the boxes for the .NET framwork and the .NET sdk  documentation.
From what I can see the install went fine, I was able to start Vs.NET and
select a project type and all.

I can only guess that the VS.NET installer  did not recognize the .NET
framework install becuase it was patched with SP1, thus the versions didnt
match. This would be typical of Microsoft installers :). Anyway, just
wanted to detail what I did in case anyone else ran into the same problem.

One thing ... in SQLDeveloper edition you can create more than one instance of
SQLServer .... I called my second one local\NetSDK .... then I don't have to
install msde from VS set up and the config is under my control. Then run the
.NET db files, it looks for the local\NetSDK instance
(FrameworkSDK\Samples\Setup\ConfigSamples.exe).
And I don't have a floating msde installation and/or folders around the place
when I don't really know what or where it is.

All I can say to this is it "probably" does exactly what I did, and just makes
another installation but using minimum files  and no enterprisemanager as it's a
freebie. MS know what their doing and all that - but I have to say I'm happier
making my own local\NetSDK install.

Now you know that as well, you'll probably consider wiping your machine and
starting again and having a perfectly clean and correct set up with zero
installation hitches so you can be that much more confident that when something
does go wrong then it isn't down to the installation of it all.

And do it all again now before you spend 3 days installing the rest of your
software and software settings.

And if you do decide to reinstall the whole cahoot, then test creating a second
instance of SQLserver on your current set up.

Sorry to install  nagging doubts in your mind, but don't blame the install ! What
a mess to start with eh ????
(and save altered samples to cd or another folder && copy && change "QuickStart"
to "QuckStart2" in C:\FrameworkSDK\Samples\Setup\Setup.xml so one original set
of samples and one experimental version - actually that won't work  as the VR's
havent got paths associated with them)

Start again .... I would .... go ooooon.
Wendi lets out a sign and her eyes dim, thinking ... Oh gaawwwwddddd, not all
that palaver again.

I didnt install  MSDE from VS.NET. That was another box I unchecked.