Why is my customer portal daily build show MVC5..... shouldn't be 6.....
thanks a lot.
Why is my customer portal daily build show MVC5..... shouldn't be 6.....
thanks a lot.
Hi Jean-Marie,
It would see there is a problem in our build process not providing the latest build. I put a request into the appropriate resource to check in on this.
Hi Jean-Marie,
The updated MVC 6.0 Daily Builds are now available.
------- Thanks... try to replace my initial DLLs and now I get this when I want to execute the application.
---------------------------------------------------------
Line 70:
Line 71: @{
Line 72: Html.ThinkGeo().Map("Map1") Line 73: .MapBackground(new BackgroundLayer(new GeoSolidBrush(GeoColor.StandardColors.White)))
Line 74: .CurrentExtent(-14148507.181077, 6271924.7354557, -5114687.7715466, 3097880.0780531)
Source File: c:\VSTS\GeoWeb\GeoSpatial\GEOWEB_MVC_SW\Views\Shared\Index.cshtml Line: 72
Stack Trace:
[TypeLoadException: Could not load type 'ThinkGeo.MapSuite.Core.Feature' from assembly 'MvcEdition, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null' due to value type mismatch.]
yRM=.8BU=.MBY=(Object MRY=) +0
ThinkGeo.MapSuite.MvcEdition.Map.ohQ=() +145
ThinkGeo.MapSuite.MvcEdition.Map.Render(HtmlTextWriter htmlTextWriter) +1296
ThinkGeo.MapSuite.MvcEdition.MapBuilder.Render() +125
ASP._Page_Views_Shared_Index_cshtml.Execute() in c:\VSTS\GeoWeb\GeoSpatial\GEOWEB_MVC_SW\Views\Shared\Index.cshtml:72
System.Web.WebPages.WebPageBase.ExecutePageHierarchy() +197
System.Web.Mvc.WebViewPage.ExecutePageHierarchy() +97
System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage) +76
System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance) +260
System.Web.Mvc.BuildManagerCompiledView.Render(ViewContext viewContext, TextWriter writer) +115
System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context) +295
System.Web.Mvc.ControllerActionInvoker.InvokeActionResult(ControllerContext controllerContext, ActionResult actionResult) +13
System.Web.Mvc.<>c__DisplayClass1a.<InvokeActionResultWithFilters>b__17() +23
System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func`1 continuation) +242
System.Web.Mvc.<>c__DisplayClass1c.<InvokeActionResultWithFilters>b__19() +21
System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult) +177
System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +89
System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +102
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +57
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +43
System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +14
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +62
System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +57
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +62
System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +47
System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +25
System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
System.Web.Mvc.Async.WrappedAsyncResult`1.End() +62
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +47
System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9629708
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
Hi Jean-Marie,
Did you update all of the dlls that were provided, such as MapSuiteCore.dll or did you just update the MvcEdition.dll?
Yes of course!
Hi Jean,
We’ve changed the Feature from struct type to class type since 6.0.36.0, so that means in production build the Feature is still struct type, which is class type after 6.0.36.0, I made a test that reference the MvcEdition.dll from the production build, and MapSuiteCore.dll from the latest 6.0.180.0 package, I get the same result as yours. Could you please tell me the version of dlls you downloaded so we can confirm it’s a bug in the daily build or not?
Thanks,
Edgar
I have the version from my customer portal. I guess 6.0.0
Look at my customer portal DLLs for the daily build.
Hi Jean,
We need to know the version numbers of the exact dlls that you have referenced in your application. Edgar was able to recreate the problem with specific versions of the dlls so we need to know the exact versions you have referenced as well.
Hi,
sorry for the delay!
Current MVC is what I have downloaded from my customer portal 6.0.0.0
now daily build was : 6.0.186.0
So can you run your program correctly with 6.0.186.0? It just works fine on my side, if it still not work, our support team will send you the dlls of version 6.0.186.0.
Regards,
Edgar