This blog is no longer updated please visit http://www.createdbyx.com/ instead.

Thursday, November 10, 2005

Woops forgot to mention

I forgot to mention in my last post there is a web page detailing how to uninstall previous beta versions of the express line of products as well as providing a auto uninstaller to automate the process. I used the auto uninstaller to remove the .NET and express beta without any problems

http://msdn.microsoft.com/vstudio/support/uninstall/default.aspx

Visual Studio Express! Absolutely Free until Nov 7, 2006!

Microsoft has officially released the Visual Studio Express suite of products. And get this, There all free! But only until Nov 7, 2006. After that MS plans on retailing the software for about $50. And anyone who downloads it now does not have to pay for it afterwards. For more details Click Here...

I think this is a great opportunity for legacy VB6 developers to jump on the .NET bandwagon. I have been using VB Express since beta 1, and I have to say even though it does not support IDE Macros as well as some other Pro level IDE features it is still a very functionable IDE.

Here's the thing you really need to know about the new express editions. The Visual Studio IDE is just an application that helps you write your code. It has nothing to do with compiling your code. The .NET framework is responsible for doing the compilation of your apps. (IE the new MSBuild system) So even though you may not get all the bells and whitles in the express versions of the Visual Studio IDE that is not to say you will not be able to take full advantage of the power of the VB.NET, C# or other .NET languages.

Like I said I have been using VB Express since beta 1, and I think if you are as cheap as me, and don't want to have to dish out $2000+ CAD again to get a MSDN Pro subscription then I recommend you do what I am going to do and start using Visual Studio Express!

Monday, November 07, 2005

DotNetNuke Configuration Errors

I have been working on my new website but I have had conflict problems with the DotNetNuke portal that the current site uses. And as such I can only test my new site on my desktop and not online.

So in the comming weeks you may see my site loose some of it's dnn content as I slowly convert the content into their respective rss feeds. I will try and find a way to publish links to the new content feeds for the new site as I make progress.

So far it's looking like a promising idea to use a 100 percent rss driven website. But I guess only time will tell.