1

I'm trying to load an assembly that was installed as part of .Net 3.5 SP1 using Assembly.Load() by referencing its strong name. This works fine on my computer right now, but is it future proof?

Will the strong name of core .Net assemblies change when patches are installed or new versions of the .Net framework are released?

Edit: If .Net 5.0 includes a massive rewrite of System.Data, will the strong name I am using now break my app on that platform?

Martin
  • 37,119
  • 15
  • 73
  • 82
Ryan Michela
  • 8,284
  • 5
  • 33
  • 47
  • 2
    The way to fix this is to use partially specified names, and use partially qualified names, and fully qualify them in the .config file. http://msdn.microsoft.com/en-us/library/fb1c06s6(VS.85).aspx – codekaizen Jun 17 '10 at 22:05

1 Answers1

1

Patches like service packs will not change the strong name of the assembly. That would be a too big of a breaking change to include in a service pack.

Strong names will change between major versions of the framework since the version number is included in the strong name.

JaredPar
  • 733,204
  • 149
  • 1,241
  • 1,454