cathal connolly wrote
the version's aren't actually "dualing". .net strongly types and versions it's assemblies, so they can all work in whats known as "side-by-side" mode. I have a machine where I run 1.0, 1.1, 2.0, 3.0 and 3.5 on it, as well as vs.net 2003, vs.net 2005 and vs.net 2008, and all versions work seamlessly without interupting each other. If you're running vs.net 2005 you'll need to keep 2.0 on the machine. As for applications written in 1.1, if you have any then they're binary compatible in 2.0 e.g. you can run a website compiled in 1.1 under IIS with the mappings set to 2;0.
I don't have any apps at all on my home machine, at least done in any version of VS etc, so I guess I'm good to go for dumping at least 1.1. I'll go ahead and hang on to the others tho.
I think the answer you got from the other list may be correct. I know that if you install IIS before the .net framework the asp.net mappings are not created and you have to run aspnet_regiis -i, but i never thought that it would create the aspnet user as well - now you've pointed that out it makes logical sense. If I was you I would try that first, as it's likely to resolve your issue.
And in fact it did fix that particular problem of the "lost" aspnet user. However, it was interesting that when I first tried it under the L&G version I had, 3.5, it did NOT recognize the command, nor under 3.0. However, when I went back to 2.0, it found it, ran it, and all was well. I guess if nothing else this proves I definitely have to keep 2.0 around :) Which is perfectly fine :)
So on to the next phase of the DNN journey. Thanks to all who responded! I'll probably be back here with my next challenge :)
elaine