Re: [mapguide-users] 64-bit woes

2014-05-27 Thread Liglio
Hi Greg, I know this is an old post, but I have the same problem. I think that by now you have resolved this issue. I have VS 2010 in a window 7 64 bit. I have mapguide web api 64 bit installed, I am using IIS as web server, my application has mapguide pool. All my stuff is in 64 bit, I run VS

Re: [mapguide-users] 64-bit woes

2014-03-27 Thread Hans Milling
Are you using Visual Studio? Go to the Debug menu and select Exceptions. Then at the Common Language Runtime Exceptions mark in the checkbox Thrown. This will notify you of any exceptions that might happen behind the code. You can also try to step trough the code. If you pull the Maestro5 source

Re: [mapguide-users] 64-bit woes

2014-03-26 Thread frosty1_4me
Hey Hans, I attempted to create your tool, I thought it was a great idea. I created an empty console project and pasted your code into a new class. The exe was created when compiling the code. I took that exe and placed in the bin folder where my dll's where and ran it. The console doesn't

Re: [mapguide-users] 64-bit woes

2013-04-29 Thread Hans Milling
According to M$ the error code 4 means: Initialization error occurred. There is not enough memory or disk space, or you entered an invalid drive name or invalid syntax on the command line. My best guess is that the compiler (like visual studio) is 32 bit and when trying to copy from Program Files

Re: [mapguide-users] 64-bit woes

2013-04-28 Thread Jackie Ng
Those dlls in question are not .net assemblies. I don't know why VS would try to process them for metadata. Maybe because they're dlls in your output directory. Either way it should not be an issue. Local IIS debugging means that IIS will probably still have open handles on your dlls from a

Re: [mapguide-users] 64-bit woes

2013-04-26 Thread Greg
I am using the local IIS Web server for debug. I am running vs as administrator. I must be doing something else wrong. My build and Intellisense outputs are below. Is it possible that some of my other project references are causing a problem? /- Build started: Project: Cid_Map,

Re: [mapguide-users] 64-bit woes

2013-04-26 Thread Greg
I have additional information: I changed the platform target in my project from x64 to any cpu and my IntelliSense problems went away. I still get the build error when the dll files are copied from the nuget packages (see below). If I stop the local IIS server during build, the error goes away.

Re: [mapguide-users] 64-bit woes

2013-04-25 Thread Greg
I am suddenly getting the following error when I build my project using Jackie's nuget package and don't know what to make of it: The command xcopy /s /y C:\Program Files\OSGeo\MapGuide\Web\www\Cid_Map\packages\mapguide-api-base-x64.2.5.0.7449\mapguide-api-base\*.* C:\Program

Re: [mapguide-users] 64-bit woes

2013-04-25 Thread Jackie Ng
If you're debugging using the built-in web server, stop. That web server is a 32-bit process that *cannot* run 64-bit ASP.net applications. If you want to debug a 64-bit ASP.net web application, it has to be through local IIS, which normally means you have to run Visual Studio as an

Re: [mapguide-users] 64-bit woes

2013-04-12 Thread Hans Milling
Hi Greg If you do not have any references to the MapGuideDotNetApi.dll then just delete it. That is what I did. I am using the Maestro API, and I modified it and deleted the reference to the old MapGuideDotNetApi.dll and added the other DLL files as references. This works flawless. Hans... --

Re: [mapguide-users] 64-bit woes

2013-04-12 Thread Hans Milling
Oh, and by BTW, I created a small command line tool to check all .exe and .dll files in a folder. The tool will display if binary files are x86, x64 or Any (in case they are .net). Also version numbers are displayed. Just copy the tool to the location of your binary files and double click it. All

Re: [mapguide-users] 64-bit woes

2013-04-12 Thread Greg
Thanks Jackie and Hans for your suggestions. I decided to: - remove all mapguide references - delete all mapguide dll's from my application\bin directory - install the mapguide-api-web-x64 nuget package - rebuild and all is working now. Thanks again. Greg -- View this message in context:

Re: [mapguide-users] 64-bit woes

2013-04-11 Thread Greg
I know this is an old post but with the release of 2.5 I am upgrading and am hoping to get a few ideas. I need to develop for Windows Server 2008 R2. My development machine is: Windows 7 64 bit Visual Studio 2010 IIS 7.5 MGOS 2.5 64 bit I have installed the 64 bit version to my development

Re: [mapguide-users] 64-bit woes

2013-04-11 Thread Jackie Ng
You cannot debug 64-bit ASP.net MapGuide applications through the built-in VS web server as that is a 32-bit application. This is the default choice for ASP.net applications. You have to debug though local IIS (it's some project setting in there) You have to UAC-elevate VS in order to debug with

Re: [mapguide-users] 64-bit woes

2013-04-11 Thread Greg
The only Mapguide references in my project are: OSGeo.MapGuide.Foundation OSGeo.MapGuide.Geometry OSGeo.MapGuide.MapGuideCommon OSGeo.MapGuide.PlatformBase OSGeo.MapGuide.Web and I have copied all dll's from the mapviewernet\bin folder When the project is loaded I get the following output:

Re: [mapguide-users] 64-bit woes

2013-04-11 Thread Jackie Ng
Unless there's a reason you can't, I'd unref and remove the existing DLLs and just install the MapGuide nuget package via the nuget package manager in VS http://nuget.org/packages/mapguide-api-web-x64/ This way you don't have to concern yourself with whether you copied the correct dlls. The

[mapguide-users] 64-bit woes

2011-12-23 Thread _Jon_
Hello, I have developed a site on MGOS 2.2. I built the (.NET) site on a 32-bit windows 2008 development machine, which is not my primary development machine. I am now trying to get the site to build on my 64-bit Windows 7 development machine, and I am having trouble. The strange part is that