Hi Kenneth,
thank you for your clarification. I've got it running with the solution you
mentioned. I added an entry to the PATH env variable that points to the bin
folder of my FDO SDK. That's a solution for my development environment. But
when I release our WebApplication to our costumers I thin
When running a WebApp the actual assembly is placed in a temp folder.
You can read System.Reflection.Assembly.GetExecutingAssembly().Location,
to see it.
The windows dll location algorithm looks in the current dir, then
searches path, etc.
You need the dll's to be in the PATH env paths, you also
FDO needs the VC++ runtime library. The OSGeo.FDO.*.dll files are .net
wrappers around the native libraries which use the VC++ runtime. Do not
uninstall it.
The fact that you have it working in a windows application means that you
have the runtime library installed. It also means that there is de
Using the SDK File in a WindowsApplication works for me!
But I would like to manage the creation of a feature source in the
WebApplication.
I think I have the C++ runtime library installed but I don't know exactly.
How can I determine that I have Visual C++ 2008 runtime library installed? I
don'
Do you have the Visual C++ 2008 runtime library installed?
If so, I wonder then if it is because you are using this in an ASP.net
environment and that is somehow messing with the paths?
- Jackie
Gunter Becker wrote:
>
> OK, I tried it with the SDK files and know I got the error message:
>
>
OK, I tried it with the SDK files and know I got the error message:
"The specified module could not be found"
Any ideas?
Gunter
Gunter Becker wrote:
>
> No, these files are from "FDO API and Common Binaries" under "Windows
> Binaries". Does it make a difference?
>
> I'll download the SDK fi
No, these files are from "FDO API and Common Binaries" under "Windows
Binaries". Does it make a difference?
I'll download the SDK files an give this a try!
Gunter
Jackie Ng wrote:
>
> These dlls are from the FDO SDK?
>
> Make sure that *all* the dlls (and providers.xml) from your FDO SDK are
These dlls are from the FDO SDK?
Make sure that *all* the dlls (and providers.xml) from your FDO SDK are in
the output directory
- Jackie
Gunter Becker wrote:
>
> Thank you Jackie,
>
> I've put all the managed and unmanaged dll's from the windows binaries in
> the bin folder of my WebApplica
Thank you Jackie,
I've put all the managed and unmanaged dll's from the windows binaries in
the bin folder of my WebApplication and tried to follow your steps but I got
an error message :
File or assembly "file:///C:\Users\gunter.becker\Documents\Visual Studio
2008\Projects\CSOGIS\bin\Expressio
The ".. such files" refers til SHP/SDF/SQLite files.
I have not used the FDO API enough to answer your FDO question.
Regards, Kenneth Skovhede, GEOGRAF A/S
Gunter Becker skrev:
Thanks Kenneth,
which files do you mean with "create and manipulate such files".
Do you mean the FeatureSource xml
FDO is the way to go. As Kenneth already mentioned, this approach won't be
portable unless you want to dive into the native C++ API. The Managed FDO
API is only available for Windows.
To do this, you will have to do the following:
FDO side:
1. Create a FDO connection to the desired provider
2.
Thanks Kenneth,
which files do you mean with "create and manipulate such files".
Do you mean the FeatureSource xml document or the empty SHP- and SDF-Files.
Do I have to use all of the following libraries: OSGeo.FDO.dll,
OSGeo.FDO.Common.dll and OSGeo.FDO.Geometry
Thanks, Gunter
Kenneth Skov
The MapGuide API only supports creating SDF files.
Rfc77 adresses this partially, and is being implemented for MG2.2:
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc77
You can always create a FeatureSource xml document and upload to MapGuide.
What is missing is an empty SHP/SDF/SQLite file and so
13 matches
Mail list logo
