Dan Ciruli and Nathan Trueblood will be running a webinar on the DN, showing how to speed up applications. They do a great job of giving an overview of its power and functionality. The focus of this webinar will be financial applications. Sign up to find out how our product can help you do more. Faster. Go here for details on what will be covered and to sign up. It is scheduled for 10AM Pacific and will be about 30 minutes...

Now that I am finished with the port to VS2005 / .NET 2.0, I wanted to point out a few final issues I came across. Note that we use the Preemptive Dotfuscator v3.0 here, but the obfuscation issues likely apply to other obfuscators as well: New files in ASP.NET 2.0 As the compilation model for ASP.NET has changed a great deal, there are also some new files that you must deploy. Of course, this is not an issue if you use VS2005 to deploy directory to a web site, but if you are packaging up all of your...

I have posted a bit on merging ASP.NET 2.0 (without aspnet_merge) and also on renaming ASP.NET 2.0 auto-named assemblies. My first solution on renaming was incomplete in that it would only work when there were no dependencies between the renamed assemblies. This solution is correct and produces assemblies that properly get through Dotfuscator 3.0 / and actually run! All of the code below are either nant targets or nant tasks. These should be generally applicable (with the right properties assigned)....

After much speculation by many (on whether or not it would be before the 7th), it is available. This is good news for those of us exhibiting at the VS launch -- we will be able to show off the Digipede Network from the final Visual Studio

I found an error in my ASP.NET 2.0 assembly-renaming script (see Renaming ASP.NET Assemblies). The regular expression isn't matching all assembly names that might be generated by the compiler. This expression does the trick: (?'assembly'App_Web.+\s*)\042 Simply replacing the pattern in the nant regex task solves the problem...

Dan is off to Code Camp in Seattle this weekend. He'll be talking on Sunday @ 3 about grid-object oriented programming (what he calls GOOP). He'll be talking about that and showing the Digipede Network at the same time. If you are going to be there drop by and see him

Where, I don't know. It isn't yet on MSDN. Robert Scoble said that it (and SQL Server 2005 + BizTalk 2006) are done in Three VPs on Channel 9. Tonight is the shipping party. Congratulations to all of the teams at Microsoft that have been working on this

I have removed this solution in favor of a new, more robust, solution. You can find it on my new blog, here: Renaming ASP.NET 2.0 Assemblies Redux

This post and more can be found on my active blog, here. Apparently Microsoft will be releasing a tool called aspnet_merge that will help resolve some of the shortcomings in the deployment options when precompiling ASP.NET 2.0 projects. This is supposed to be available on November 7th, but I don't feel like I want to wait. Thanks to the DotNetNuke guys for working with Microsoft on this. I'm really surprised that it got to be so late in Microsoft's development cycle before they figured out this was...

I probably have not been clear in my previous posts about the overall methodology I'm following in our port to VS2005. I have split my porting process into several different steps to isolate the effort into manageable slices. These include: Porting the projects into VS2005 for ongoing development. While doing this, I have insured that everything still builds with VS2003 while my team makes the transition to the new IDE. I am avoiding the temptation to fix the thousands of warnings related to deprecated...