Making an ASP.NET 4.0 Website work with 3.5 Virtual Directories Under It

One might assume that a parent website application set to ASP.NET 4.0 in IIS 6 would have no issue running backward compatibility for its virtual directories (VirDirs) that are still written in ASP.NET 3.5 or even 2.0… But you’d be wrong.

Here’s an example structure:

 
• MyWebsite (.NET 4.0)
• MyInsetApp1 (.NET 3.5)
• MyInsetApp2 (.NET 3.5)

Which could create URLs like this:

• MyWebsite.com
• MyWebsite.com/MyInsetApp1/
• MyWebsite.com/MyInsetApp2/

(they appear to be on the same website, but actually run as separate distinct applications)

You actually have to jump through some hoops with the web.configs for both the parent website application and the child…

Full Post >

ASP.NET 4.0, Extensionless Urls, and the eurl.axd errors

Apparently ASP.NET 4.0 has something special for “extensionless URLs”—which is what we get from using ISAPI_Rewrite on our Windows Server 2003 machines. The symptom we were seeing was that the URL Rewriting kept unexpectedly returning something similar to this:

eurl.axd/ADkfjsFiSofmaWOeiejrlErF

so rewriting something like:

/myrewrite/articleID/articleName/

would end up rewriting to:

/myrewrite.aspx?id=eurl.axd/ADkfjsFi…..

On the server’s Registry Editor (regedit) I followed this article’s “option 3” and turned off the EnableExtensionlessUrls, which is a DWORD set to 0 (zero) within HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\4.0.30319.0 —then you must run theh iisreset command-line tool.

Full Post >

VS2003 Project Load Error

Yes, this a dated topic, but like many we still have a few websites out there that were built years ago and the client doesn’t have a budget to have us upgrade the .NET versions—so we still have some sites running .NET 1.1 and we have to use Visual Studio 2003 still for those.

This post is specifically about the VS2003 error:
“Unable to get the project file from the Web Server”

Anyway, found out that if you have an issue loading a project with the above error and you’ve checked every typical thing and all seems to be fine, try this:

Delete the project cache in “C:\Documents and Settings\<username>\VSWebCache”

Worked like a charm…

Full Post >

Set Page Title in .NET Theme

.Net themes can be a wonderful thing. We use it often to apply a different look and feel based on the Domain where the page is hosted or some affiliation the user has with the site. However .NET doesn’t supply a straight forward means of changing the Title of your web pages based on the Theme being applied. I’ve found a nice easy little work around for anyone out there looking for a way to do this. Here is all you have to do:

1. Add an asp label to your page with visibility set to false and a skinID. Don’t forget the runat=“server” (e.g. <asp:Label ID=“lblPageTitle” runat=“server” SkinID=“PageTitleSkin” Visible=“false” /> )
2. Add a skin to your skins file that set’s the text of this…

   Full Post >

   Technical  //  asp-net
   0 comments