search

MapWindow / MapWindow5

MW5 is a desktop GIS which is extendable using the plug-in architecture. It is using the MapWinGIS mapping control and is created from scratch in 2015 using new technologies like MEF and Dependency Injection making it small in size, robust and fast.
288 stars 100 forks source link

Castle.Core could not be loaded #37

Closed saadb closed 4 years ago

saadb commented 6 years ago

Description: Could not load file or assembly 'Castle.Core, Version=4.1.1.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The system cannot find the file specified.

Stack trace: at Castle.MicroKernel.DefaultKernel..ctor(IDependencyResolver resolver, IProxyFactory proxyFactory) at Castle.MicroKernel.DefaultKernel..ctor() at Castle.Windsor.WindsorContainer..ctor() at MW5.DI.Castle.WindsorCastleContainer..ctor() at MW5.Program.Main()

Description: Could not load file or assembly 'Castle.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The system cannot find the file specified.

Stack trace:

pmeems commented 6 years ago

When do you get this message?

saadb commented 6 years ago

I pulled the source code and compiled it in VS2017 successuflly, and when I run Mapwindow5.exe I get the above run time error

saadb commented 6 years ago

By the way I am using VS2017 Community Edition

pmeems commented 6 years ago

We build MW5 and MapWinGIS using VS2015 Community ourself. Perhaps you are using a different package? We're using v4.1.1 of Castle.Core. We've not yet upgraded.

You did pull from the dev branch?

saadb commented 6 years ago

Yes, I pulled the dev branch When I rolled Castle.Core from 4.3.1 to 4.1.1 then no run time error related to Castle.Core

pmeems commented 6 years ago

So something changed between v4.3.1 and v4.1.1. Are you up for a challenge to find out what we need to change to use the latest version of Castle?

-- Paul

saadb commented 6 years ago

Yes, I will check it out

saadb commented 6 years ago

when using VS2017 run NuGet Package Manager for MW5.DI.Castle Update castle.core to latest version (i.e v4.3.1) and Castle.Windsor (v4.1.0) Make sure packages.config in the MW5.DI.Castle has been updated accordingly Rebuild the solution.

pmeems commented 6 years ago

Is this the solution for this problem? If so I can close this issue.

saadb commented 6 years ago

I suggest to keep this issue open for a little while, I am still chasing why the app.config is not syncing with packages.config and dependencies not updating accordingly.

pmeems commented 4 years ago

If this is still an issue with the latest release (https://github.com/MapWindow/MapWindow5/releases) could you create a new issue? For now, I close this old issue.