Install .NET Support for ArcGIS 10

7957
11
05-31-2011 09:58 AM
JamesCrandall
MVP Frequent Contributor
I cannot seem to get this installed correctly -- this is for a client running ArcGIS Desktop 10.  I thought by choosing to "Modify" the ArcGIS10 Installation it would provide the option to include the .NET Support SDK, but it does not.  I did locate a seperate .msi that is suposed to be the SDK support (its in a file folder that someone has titled "SDK_dotnet"), so I attempted to run this .msi but get the following error:

"ArcObjects SDK for the Microsoft .NET Framework requires a supported edition of Microsoft Visual Studio 2008 SP1 to proceed".

Which this of course then fails to install.

I don't get it.  I am simply trying to deploy a customized Toolbar, that I have built the Setup project for, and it's .msi --- adding a launch condition to check for .NET support.  Anyone have a tip on how to get .NET Support installed on a client (ArcGIS Desktop 10) client?

Thanks
0 Kudos
11 Replies
AlexanderGray
Occasional Contributor III
The option shows up on first install if you have the microsoft .net framework installed.  I am not sure about modify.  Do you have the microsoft Framework 2.0 or higher installed?
0 Kudos
JamesCrandall
MVP Frequent Contributor
The option shows up on first install if you have the microsoft .net framework installed.  I am not sure about modify.  Do you have the microsoft Framework 2.0 or higher installed?


Well,

Looks like this issue is the result of something else in my assembly...  I am getting a 1001 unable to install loader type error during the setup/deployment of my custom tool, so I had thought that this was because the client didn't have the .NET Support SDK installed.

...but I don't think that is an acutal requirement to get my custom toolbar installed after all.

There is something else in my project that is being referenced or something.  I am a bit unsure.
0 Kudos
RichardWatson
Frequent Contributor
So you built a custom setup and it fails when run.  You can debug this in a couple of ways:


  1. Run msiexec from the command line and enable logging (Google on voicewarmup)

  2. Perform the installation steps manually and see which references, if any, are missing.  You can identify missing references using fuslogvw or Reflector.

0 Kudos
JamesCrandall
MVP Frequent Contributor
I believe (99% certain) that this issue is the result of attempting to associate an assembly build in Debug with a Setup project.  That is, things were compiled in Release mode, but deployed in Debug/older version (or vice-versa).
0 Kudos
JamesCrandall
MVP Frequent Contributor
So you built a custom setup and it fails when run.  You can debug this in a couple of ways:


  1. Run msiexec from the command line and enable logging (Google on voicewarmup)

  2. Perform the installation steps manually and see which references, if any, are missing.  You can identify missing references using fuslogvw or Reflector.



Thanks for the tip, Richard.

I will attempt to incorporate more logging information as I run into more of these issues.  On your second bullet point, I did go thru and manually "clean" the original assembly/app (which it did have some old refs and or config stuff in there that was not necessary).  However, I don't believe any of this is the cause of my 1001 error.  But it did force me to do some house cleaning for sure.

Thanks again.
0 Kudos
AlexanderGray
Occasional Contributor III
You can also manually copy the assemblies and use ESRIRegAsm to see if that gives you any more information.  If it is missing references you will get errors. 
In some cases running a .net msi over the network can give problems, so that is another thing to check.  I still think you need the .net interop installed but with 10 I am not sure, the dotnet folder is not in the install folder any more, I would have to read up on the new things.

Cheers
0 Kudos
JamesCrandall
MVP Frequent Contributor
You can also manually copy the assemblies and use ESRIRegAsm to see if that gives you any more information.  If it is missing references you will get errors. 
In some cases running a .net msi over the network can give problems, so that is another thing to check.  I still think you need the .net interop installed but with 10 I am not sure, the dotnet folder is not in the install folder any more, I would have to read up on the new things.

Cheers


Thanks again,

You very well might need that interop, but I did manage to get the custom tools installed on a client that only has ArcGIS 10 installed (ie, no .NET Support SDK is listed in the Add/Remove programs list).

One thing to note/consider is that I am finding many organizations are implementing tight control over the IT infrastructure --- this means that very few have Admin rights in order to install and or register things as you suggest.  This makes things quite difficult because as a developer, never do things go as planned and there always seems to be hiccups along the way.

Case in point: when an install fails, it becomes a complex issue to debug simply by the nature of how the IT policies in place affect how that debug would work.  That is, I have to debug THRU the IT department now because I do not have admin rights to install things!

Hope that makes sense.  But this is something that I think more and more developers will have to deal with as IT policy within organizations become more and more restrictive.
0 Kudos
AlexanderGray
Occasional Contributor III
Thanks again,

You very well might need that interop, but I did manage to get the custom tools installed on a client that only has ArcGIS 10 installed (ie, no .NET Support SDK is listed in the Add/Remove programs list).

One thing to note/consider is that I am finding many organizations are implementing tight control over the IT infrastructure --- this means that very few have Admin rights in order to install and or register things as you suggest.  This makes things quite difficult because as a developer, never do things go as planned and there always seems to be hiccups along the way.

Case in point: when an install fails, it becomes a complex issue to debug simply by the nature of how the IT policies in place affect how that debug would work.  That is, I have to debug THRU the IT department now because I do not have admin rights to install things!

Hope that makes sense.  But this is something that I think more and more developers will have to deal with as IT policy within organizations become more and more restrictive.



I hear you, it is becoming more of a hassle.  I think that is what the addin model is supposed to address.
0 Kudos
JamesCrandall
MVP Frequent Contributor
On a different (but similar topic) note, how do I tell my setup project to add a specific file to a specific directory on the target computer/client?  I have a Crystalreport.rpt file that needs to be automatically added to the C:\Program Files\ArcGIS\Desktop10.0\Bin directory on the install process.
0 Kudos