ASP.NET 2.0 BETA 2: Hey, my ASP.NET IIS Tab is missing!

Chris Adams says this:
This is a problem caused by the change between Beta 1 and Beta 2.

To fix, check the following 3 regkeys -
HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32
HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32

Under (expand) InProcServer32, look for the presence of a non-2.0.0.0 (example 2.0.36.0) and remove it.
It has a reference that causes this to break.

If you do not have this MMC interface, you can use aspnet_regiis.exe aspnet_regiis -s
where path equals the location in the metabase where you want the mappings to change.
Note: There is also a switch to do this non-recurvisely if you desire.

and Stebner's VS.NET 2005 beta removal tool:

http://blogs.msdn.com/astebner/archive/2005/04/19/409555.aspx

Comments

  1. Anonymous5:05 PM

    You're the man, that fixed my problem!

    ReplyDelete
  2. Anonymous4:07 AM

    I have the registry OK, and the problem still persists...

    And my server DOESN'T HAVE ANY BETA OR PREVIOUS VERSION OF ASP.NET 2.0.5

    ¿What is doing microsoft with this problem?

    This is not the best way to launch .net 2.0...

    ReplyDelete
  3. Anonymous1:31 PM

    it was under HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32
    2.0.0.0 and 2.0.36.0 and I removed the Key 2.0.36.0 wow I have my ASP.NET TAB :) Many thanks Peter :)

    ZyganzY

    ReplyDelete
  4. Anonymous10:57 PM

    The regedit worked for me man, i appreciate you posting it!

    ReplyDelete
  5. Anonymous2:16 PM

    It's been a while...but thanks for the help! This fixed our issue.

    ReplyDelete
  6. jay lill4:36 PM

    I only have the 2.0.0.0 entries in the registry. However I do not see the 2.0 tab. Any thoughts?

    ReplyDelete

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more