Install web development component visual studio 2003

Friday, April 23, AM. User posted After some searching I've managed to fix the problem, it was indeed the Web Authoring Component, it has to be installed manually: 1. Extract not copy the. Run the extracted. Wednesday, May 5, AM. Monday, April 26, AM. User posted Hi, I've looked in my WCU folder and the subfolder you mentioned is not present. I know, I know — VS.

NET is not supported on Windows Vista and above. In fact Microsoft in their all-knowing wisdom went ahead and supported Visual Studio 6. NET !! NET product or to weird resource constraints or some other theory insert favorite MS conspiracy theory here.

So VS. NET for my job. The annoying dialog declaring that the program is not supported is easily dismissed — there is a check box allowing you to block it from appearing again.

Debugging needs you to run in administrator mode — you can set this by right-clicking the shortcut choosing properties and then the compatibility sub-tab — there is a check-box to always run the program as administrator.

The next challenge was VS. You can configure everything down to the individual web. Luckily running ASP. NET 1. NET — I found this article whose instructions I followed. There were some further gotchas that I encountered that you might be interested in knowing about —. NET than Windows 7. NET on Windows 7. Overall, I think Windows 7 is a cool OS but the experience for me is marred due to reality of having to coax it to work with VS.

NET Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Verify that you are a member of the 'Debugger Users' group on the server. Do you know if it is possible to run VS in Vista Home premium? Any help is greatly appreciated. I've spent more hours than I care to count trouble shooting this. Brian, Thanks this really helped. I'd been stuck for hours until I found your blog. Neil, Thanks for helping to make this all less painful for everybody.

I checked out your steps. As far as I can tell the parts that my list is missing are: 1. I actually had it disabled prior to ever attempting to install VS2k3 which is probably why I neglected to include this step.

An alternative to this would be to right-click Visual Studio in the start menu as do "Run as Administrator". I'm not sure if perhaps you didn't include that switch? If that switch doesn't work for some reason then manually enabling them like you did is important. Editing Authentication Settings - Yeah NET applications.

I have run into that plenty of times but I didn't include that in my list since the error message usually states exactly what needs to be done. For a purely ASP. NET application this step would not be necessary. It is also worth noting that you wouldn't need to enable both client-side and server-side debugging.

Server-side debugging would suffice since the remote debugging components that come with Visual Studio debug the IIS worker process from the server-side. When you run the SP1 update, did it actually change the version on the file?

My install says the SP1 ran OK, but the version is still the same. I installed Vista on a new machine this week and I looked at the version of mscorsvr. The version in-fact did change. If the version didn't change on your machine after installing SP1 then I'd guess that SP1 got installed another way, perhaps via WindowsUpdate, without you realizing it. If that isn't the case then you likely got a newer DLL through some other hotfix that didn't update the entire framework. In any case, you need to update more than just this single DLL, so if it was updated by something other than SP1, you'd still need to install SP1.

Thank you so much for this post. I greatly appreciate your work. I was frustrated trying to solve the problem. After trying all other things, VS still wasn't working for me.