ArcGIS 9.1 SP 1 Is Out
Link - ArcGIS 9.1 Service Pack 1
ESRI recommends that all ArcGIS 9.1 customers download and install this Service Pack, at their earliest convenience, to ensure the highest quality experience when working with ArcGIS 9.1.
Click here to read the issues addressed with ArcGIS 9.1 Service Pack 1. SP1 is available for ArcGIS Desktop, ArcGIS Engine Runtime, ArcGIS Engine Developer Kit, ArcReader and ArcGIS Server. SP1 for ArcGIS Desktop runs pretty large at over 60 MB so you might want to grab it before the download servers get swamped.
Update - Looks like ArcIMS and ArcSDE SP1 are “coming soon”.
Would it kill ESRI to actually digitally sign their installers? My company is giving me grief about the installer. Bah!
Getting “Unknown Publisher” is looks really bad IMO
Looks like the SDE patch is available (http://support.esri.com/index.cfm?fa=downloads.patchesServicePacks.viewPatch&PID=19&MetaID=1099). Crossing my fingers for the IMS patch. I thought I read that this service pack certifies SQL Server 2005 for SDE, and .NET 2.0 for IMS. Anyone else hearing this?
.NET 2.0 isn’t, but SQL Server 2005 is supported with this Service Pack.
Gotcha. I believe I remember you saying that before. So, looks like I’ll be jumping all over 9.2.
9.2 does support .NET 2.0. Its not even in beta yet, so it will be a while before the final is released.
I have been able to get .NET 2.0 working in 9.1 though with ArcGIS Server. I havent yet checked ArcIMS, but im sure this wont be hard to get to work.
Hello;
I had created a DLL using DotNet Framework v1…..
I posted the DLL on a Server for multiple client use.
I used DotNet Framework Wizzard to set security on Client ( ~ 100) computers to allow use of DLL.
The DotNet FrameworkV1.1 has been upgraded to Framework v2….. on all computers by the system administrators.
Framework v2… does not accept the Frameworkv1.1 DLL security settings for my assemblies.
Can I program my DLL to use a specific DotNet Framework version so that my security settings can be maintained? If so, How and where do I establish the DLL security settings?
I would like to solve this without visiting all 100 client computers every time MS upgrades the DotNet Framework.
I thought this was the point of DotNet, to end the DLL hell?
Any help would be appreciated.
Bob