Check out bug FDBK13913 on the MSDN Product Feedback Center. I submitted this bug after trying to convert a VS 2003 web application to Whidbey Beta 1 using the built-in convert project wizard. Because of the change from code-behind to code-beside, this project is incompatible with Whidbey if unchanged. Yes, there are workarounds, and I used one, but I submitted this bug because that’s what it is, and The Web team is working on the bug now. I’ve submitted some bugs that were duplicates, but this one was unique, so if I didn’t submit it, who knows if someone else would?
I’ve been using VS 2003 since I upgraded from 2002, and I’ve been using VS 2005 Beta 1 for about a month, and I’d like to share my experiences. I have them installed side-by-side on my laptop, and they play fine together, but when I installed 2005, the v2.0 ASP took over my IIS apps, so I had to run aspnet_regiis to set it back to v1.1. This problem is solved with 2005 because it doesn’t need IIS, and I don’t use IIS with it. When you run a web site in 2005, it starts a built-in webserver that runs on a random high port for just as long as you need it too. This is independent of IIS. Because of the dynamic compilation model of code-beside, I don’t have to rebuild every time I modify page code. That’s nice. VS 2005 Beta 1 has some performance bugs in its build process, however. It’s a bit slow compared to 2003, but it’ll get better. I never realized how spoiled I was with 2003 since it builds so fast (of course this should be expected). 2005 will get there, but for now I have to wait for every build. Also with my 2003 web apps, every time I rebuild, I have to wait a while for the web app to recompile and serve up the page again. With v2.0 Beta 1 this restart/recompile process seems to be improved because the wait isn’t as long.
Bottom line: VS 2003 and VS 2005 work well running side-by-side, and I even reference an assembly build in 2003 with 2005 (proof of version interoperability). I have version 2 classes that inherit from v1.1 classes. Seamless.
Sometime during the day on Labor day, the .Text engine running blogs.msdn.com and weblogs.asp.net changed for the worse.
Now, in my RSS reader, if a post is over a few lines long, the rest gets cut off, and you see a very annoying (read more)
link. Now, it’s just like the news RSS feeds that give you a headline but make you click to see the rest of the article. They want a visit to the website so that the advertising dollars come in. I have no idea what this change is supposed to accomplish but to lower the number of readers of weblogs.asp.net. I know that I don’t click on “read more“ links, and I’m really glad that .Net Junkies doesn’t do this.
I want all the content in my RSS Reader, not on a website. That’s the point of aggregating instead of “headlining“.
One thing that is very important to know about ASP.NET development: To get intellisense on web controls, you must have the .aspx file open. Since the code-behind has changed to code-beside, your code file is not a full class but a partial class, so if you have a textbox in your aspx (txtInput), the variable doesn’t have to be declared in your code file. You can just type txtInput.Text = “foo”; in your code file, BUT if you only have the code file open, you won’t get intellisense on the TextBox. To get intellisense for web controls on your web form, open the aspx file. This threw me for a bit until I figured out this quirk.
I’ve finished downloading the more than 3GB required to install Team System CTP, but I haven’t had time to install it yet. I need to get my second computer online, and then I can run two VPC’s on it.
Darren Jefford has a very informative post about installing the system. It’s not something to just slap on your main laptop. You need an “environment” to test this puppy out.
I was just combing through my referral logs, when i saw a link to my “How to track down memory leaks” post coming from Experts-Exchange. That means that someone is paying to see a solution to a problem that just refers them to my blog. Has anyone reading used Experts-Exchange? For one, I find that those who claim to be an expert are often times not, but the real experts don’t claim it, they are attributed this title by their peers. Charles Petzold (whom we can all agree is an expert on Windows programming) is an example of this. If you listened to hime on .Net Rocks a few weeks ago, it’s obvious.
In my experience, I’ve been able to find solutions to my problems on the free Internet without having to pay an aggregation service. I contribute to newgroups more often than I post questions, and I can only hope that my blog is helping some people.
I have big reservations about this pay service that seems to be getting bigger. It would be harmful to the development community if more and more useful resources became pay-per-view.
I’ve set up a new URL for my blog, although it will continue to be hosted by .Net Junkies. Nothing has changed, really, I’ve just wrapped my blog site with my own domain wrapper: JeffreyPalermo.com, which just goes to the .Net Junkies site, and my RSS feed is http://jeffreypalermo.com/rss.aspx.
This is just a new forwarding name, so all .Net Junkies URLs will continue to work unchanged.
If anyone of you would like your own URL for you blog, GoDaddy.com offers good prices with free domain forwarding so your domain will point to any existing site, and you can also add sub-domains (http://photoalbum.mydomain.com), and you get free email aliases (me@mydomain.com) would point to your existing email account.
In ASP.NET v2.0, we’re benefiting from master pages and themes. Themes not only sets the stylesheet that is applied to the page, but it also has the ability to set properties on server controls. If I want all <asp:LinkButton/> controls to NOT cause validation, then I can implement a Theme line item:
<asp:LinkButton runat=”server” CausesValidation=”False”/>
and then every <asp:LinkButton/> will have that property set automatically.
When implementing master pages also, you have to think, “what themes are compatible with this master page?” Especially if you have graphics, and your theme is going to change color, your master page has to have another set of graphics to support this new color, so the two aren’t always independent.
These are great features, and we’ll all surely use them in all our ASP.NET 2.0 projects.
It’s curious how I never read people talking about .Net Overdose. dotnetoverdose.com points to the dotnetjunkies website, so I’m not sure if dotnetoverdose is going to go away, or what, but it’s a URL mast for dotnetjunkies.com. Very curious.
Here’s my blog on .Net Overdose
I did a Google search for “Jeffrey Palermo” today, and over 600 hits were returned. The vast majority of them were actually my websites. My blog dominated, but also my various websites and newsgroup posts that had been cached by Google. One very interesting site about which I did not know was BlogShares. It ranks every blog and catalogs the incoming and outgoing links and gives a valuation much like a stock. Here the valuation on my blog. $2,111.27.
