[mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010

[Trevor Wekel]

Hello Mars,

We should only move MapGuide to Visual Studio 2010 if FDO is also moving to Visual Studio 2010.  I have seen unusual application behaviour with the FDO GDAL Provider in MapGuide when mismatched dlls are used.

Regards,
Trevor


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Mars Wu
Sent: March 30, 2011 8:21 PM
To: MapGuide Internals Mail List (mapguide-internals at lists.osgeo.org)
Subject: [mapguide-internals] Request Feedback: Support Vistual Studio 2010

Hi all,

I'd like to get your feedback about moving MapGuide to VS2010, both project files and compiler.

Bruce has posted a RFC last year about moving MapGuide to VS2010 project while keeping the code compiled with VS2008 compiler. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc104
This RFC was adopted but not yet completely implemented. Now a year has passed maybe we could move one step further to move MapGuide to also VS2010 compiler.

As the first step, we might keep the source code still compile with VS2008 and do some porting to make it also compile with VS2010 compiler. (The VS2008 project files are still available).

Could you share your feedback and concerns for this move? Is there any risk from your point of view (e.g. we already know some 3rd party components don't have VC10 built binaries)?

Thanks,
Mars
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals