.NET Answers

Anyone familiar with CSS knows that classes are generally reserved for controlling how an element looks (font, color, size, etc) and rules are generally reserved for where the element is positioned on the screen.  The reason for this is that rules correspond to the id attribute of the elements on the screen and if you are using well formed html, you can only have one element on the page with any specific ID.  That is, IDs are unique.

However, ASP.NET uses that exact same feature of IDs… that they are unique.. to ensure that an ASP.NET control or an HTML control with the runat=”server” attribute set also have unique IDs, and this is where all the problems start.

(more…)

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

So, I routinely need to test the web sites I create in both IE7 and IE6.  I wouldn’t care so much about IE6 if it weren’t for the fact that some people will never be able to upgrade to IE7 without upgrading there operating system and there are a few who won’t be able to even upgrade their OS without buying a new computer.  So, that leaves us with a significant number of users who are still using IE6 for the foreseeable future.

(more…)

What? DNN 4.7?

Seems like I just get one upgrade installed and there is another upgrade ready to go.

So, what’s this HumanFriendly thing?

Currently, in DotNetNuke, we can turn on Search Engine Friendly URLs.  What this does is embed the parameters in the URL so that you don’t end up with ?variable=value at the end of your url.

That’s cool.  But, there are two REALLY big problems with this.

First, if the tabid for the page changes, your url will change.  This makes it practically impossible to “version” your pages in such a way that the search engines don’t care unless you implement some sort of 301 redirect every time a new page is created to replace the old page.

Second, it’s very hard to tell someone over the phone.  “Just go to http://www.dmbcllc.com/mypagename/tabid/45/default.aspx.”  With HumanFriendly turned on, you’ll be able to tell them, “Go to http://www.dmbcllc.com/mypagename.aspx”

DotNetNuke > Community > Blogs - Turn on HumanFriendly URLs in DNN 4.7.0

del.icio.us Tags: dotnetnuke,humanfriendly urls

Technorati Tags: dotnetnuke,humanfriendly urls

OdeToCode.com (K. Scott Allen) reports that a reference implementation to ECMAScript 4 (aka JavaScript 4) was released yesterday.

What you’ll notice right away when you start looking at the Language Overview Whitepaper is that it looks a whole lot more like CSharp/C++ now.  Complete with interfaces, real classes, and a bit of typing, ie int, string etc, the language has zoomed past the hack it has been to a full featured language.

K. Scott Allen : ECMAScript 4 – Kitchen Sink Included

del.icio.us Tags: javascript,ecmascript

Technorati Tags: javascript,ecmascript

For those of you like to get the latest and greatest. DotNetNuke 4.7 just release with support for HumanFriendly URLs.  What are “Human Friendly URLs?”

Find out right here, tomorrow.

DotNetNuke > Products > Downloads

Technorati Tags: dotnetnuke,releases

del.icio.us Tags: dotnetnuke,releases