"NOTE: You cannot use Visual Web Developer (VWD) with the Source version as VWD does not suport Class Libraries."
(groan) If I had read that one sentence about 4 hours ago, I would have stopped trying. :(
I realise it's early days for DNN 4 but it'd be great to have some kind
of list of the late-breaking pieces of info that could really save
time. (I already mentioned that in
a comment to one of your blog entries.)
It's taken me about a week to learn two very important facts about
installing DNN 4. (Granted a lot of the time was installing,
re-installing and un-installing VS 2005 Beta 2)
1) DNN 4.0.0 will not compile in
Visual Studio 2005 Beta 2 because the version of .NET Framework included in the Beta 2 is out of date.
2) DNN 4.0.0 (source version) will not open in
Visual Web Developer because it does not support Class Libraries.
This means I have no mechanism for compiling the source version until I
upgrade VS.NET 2003 to VS 2005. That's ok, I suppose. Now that I know
it's just plain impossible with VWD, I can stop trying :)
Sudden thought - does this mean I can't make new modules for DNN4 until
I buy VS 2005? That would be a disaster! The only alternatives I see
are:
1) Use VS.NET 2003 to make modules. They would be on a previous version
of ASP.NET, though. Can you mix dlls together from different versions
like that? I'd be very surprised if that worked.
2) Use VS 2005 Beta 2 to make modules. This would be ASP.NET 2.0 but
since it's incapable of compiling DNN, I doubt it would be acceptable
for module development.
Oh dear, I get the feeling I need to buy VS 2005 quite quickly here...
+ Ken Lyon
+ tabletopsoftware.com