Robert McLaws: FunWithCoding.NET

Public Shared Function BrainDump(ByVal dotNet As String) As [Value]

News

<script type="text/javascript"><!-- google_ad_client = "pub-4330602465258980"; google_hints = "ASP.NET, VB.NET, C#, C#.NET, WindowsForms, .NET Framework, VS2005, Visual Studio, XAML, WinFX, Windows Workflow, WPF, WCF, Atlas, NetFX3, Visual Studio Orcas"; google_ad_width = 120; google_ad_height = 240; google_ad_format = "120x240_as"; google_ad_type = "text_image"; google_ad_channel ="4997399242"; google_color_border = "B6C9E7"; google_color_bg = "EFEFEF"; google_color_link = "0000FF"; google_color_text = "000000"; google_color_url = "002C99"; //--></script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>
<!--
-->

You should feel free to challenge me, disagree with me, or tell me I'm completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever. That said, I will most likely only delete abusive, profane, rude, or annonymous comments, so keep it polite, please.

Blogroll

Cool .NET Articles

My .NET Tools

My Builder.com Articles

My MSKB Articles

Dude, Where's My Reference?

My next Builder.com article is finally online. This one talks about how to deploy server control files, and how to make sure they show up in the “Add References” dialog box. It's one of those steps that is often overlooked, but critical to customer usability. If server controls are your thing, then this article is for you. As always, feedback is welcome and appreciated.

By the way, the title of this post was the original title of my article. My editor never likes my titles. <shrugs> oh well. The one he came up with was much... longer.

Posted: Jan 23 2004, 09:45 AM by interscape | with 6 comment(s)
Filed under: , ,

Comments

Tim Hitchings said:

In your article you describe how you need to use HKLM\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders
I believe you will find that works well for Studio 2002 but not for 2003 and future versions.
Microsoft in their infinate wisdom changed the registry location.
For 2003:
HKLM\SOFTWARE\Microsoft\VisualStudio\7.1\AssemblyFolders
For future versions modify the 7.1
# January 23, 2004 12:42 PM

Tim Hitchings said:

I note in your article you use [TARGETDIR]\v2.0\Redistributable\For .NET 1.0. for your location.
I found it easier to not hard code any part of the location by using directory property where the product is installed. That way when version 3 comes out you don't have to remember to update the path location in your registry entries.
# January 23, 2004 1:03 PM

Robert McLaws said:

Unfortunately, you have to keep directory information in situations where multiple versions of an assembly need to reside on the computer. Often times you should not overwrite old versions for compatibility reasons, especially if you're not following my suggestions on component versioning.

I'm going to look up what I posted about RE: registry locations, and check what we're doing in our installers. I'm pretty sure we're using the original location and it works in 2002 and 2003.
# January 23, 2004 3:37 PM

Tim Hitchings said:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vstch_multivercomponent.asp
# January 23, 2004 5:57 PM

Robert McLaws said:

So, if I read this document correctly, it still looks in the old location too, meaning that the article remains correct. Is that right?
# January 23, 2004 6:05 PM

Tim Hitchings said:

Looks that way. First time I've seen the article. I just searched on assemblyfolders and it popped up and I thought I'd pass it on. My previous post was based on my experience which preceeds that article quite a bit. I write to both local machine locations. And to future locations. I can't recall but I do believe that we ran into install errors if we did not write to both locations. Examining my registry entries shows a number of other .NET vendors are also writing to multiple locations.

I burned many a long weekend when .NET first came out trying to install everything properly. Got a few hours and I'll tell you the horrors of trying to install help2 into visual studio.
Best.
# January 23, 2004 6:22 PM