Yesterday I mentioned that the final release of the Web Deployment Project for Visual Studio 2008 was out.
I installed it and ran into one small little issue you’ll want to know about if you have projects that were using the CTP release.
Back in December, I wrote that the CTP, in its attempt to not overwrite existing files if the build fails, required your post build steps to also work off of the tembbuilddir directory.
This is no longer true. We can now use the post build steps against the release or debug directories the files end up in.
I’m not sure this is a good idea, but I imagine much brighter people than I battled out the decision to do this.
If you're new here, you may want to subscribe to the mailing list to get notifications of new post and a virtual tour of past topics. Thanks for visiting!
Related Post
DotNetNuke Modules – Creating Base Modules
Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it wrong, which...
VS 2008 Web Deployment Project Support
Scott Guthrie reports that the Web Deployment Project final release is now available here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=0AA30AE8-C73B-4BDD-BB1B-FE697256C459&displ...
DotNetNuke Modules – Install DNN into VS 2008
Today, we will install DotNetNuke into Visual Studio so that we can create our first module. So fire up Visual Studio, and let's get going.
I'll be using Visual Studio 2008 to walk you thro...
Installing Silverlight2 Tools for Visual Studio
I was talking with a friend of mine a couple of days ago about the future of web development and XAML specifically when he made the comment about the tools not being available for the average deve...
Using The LINQDataSource
There is a new datasource control available in Visual Studio that works in much the same way as the SQLDataSource and the ObjectDataSource. While I would argue that the LinqDataSource is better th...