Hi, I am converting my existing working project from MVC5 to MVC6 by creating a new MVC6 project and moving things over bit by bit.
I have run into a strange issue with [ComboDataSourceAction]. In my old MVC5 project it works fine, but in my new project it returns different JSON (just containing the IDs, not the text I want to display):
[ComboDataSourceAction]
public ActionResult ClientComboData()
{
IEnumerable<ClientName> clientNames = GetClientNames();
return View(clientNames);
//return Json(clientNames);
}
If I swap in the commented out line, it seems to return Json with the names included and display them in the combobox and the drop down list shows them correctly but when I type anything in the autocomplete I get the following error:
Unhandled exception at line 26, column 4876 in http://localhost:62643/ignite ui/js/infragistics.lob.js Unable to get property 'locale' of undefined or null reference
Here is the class it is serializing:
public class ClientName
public int ClientId { get; set; }
public string FileAsName { get; set; }
Here is the content of the JSON when I hit F12 in IE and look at the network traffic.
[{"ClientId":1180},{"ClientId":1516},{"ClientId":990},{"ClientId":1212},{"ClientId":754},{"ClientId":1216},{"ClientId":1190},{"ClientId":516},{"ClientId":817},{"ClientId":1741},{"ClientId":969},{"ClientId":818},{"ClientId":620},{"ClientId":318},{"ClientId":954},{"ClientId":984},{"ClientId":1007},{"ClientId":603},{"ClientId":858},{"ClientId":973},{"ClientId":394},{"ClientId":1346},{"ClientId":348},{"ClientId":1565},{"ClientId":552},{":totals:":"1380:1380"}]
How can I fix this?
I have read an article that the next asp.net mvc 6 will be based on new fundamentals comparing to previous asp.net mvc releases . so i have these questions:-
when asp.net mvc 6 be officially released ?
what are the major differences will be between asp.net MVC 5 & asp.net MVC 6 ?and are these changes quite big comparing for example between the changes from asp.net mvc4 to asp.net mvc 5 ?
HeyYou lost your windows recovery key. And looking for new key visit
Windows 10 product key
It released on 6 November 2014 ASP.NET MVC 6.0.0-beta1 version and major differences will be between asp.net MVC 5 & asp.net MVC 6 are as followsDifference 1 – Without precedent for the historical backdrop of ASP.NET, you can run ASP.NET 5 applications on OSX and Linux. Give me a chance to rehash this. ASP.NET 5 applications can keep running on Windows, OSX, and Linux. This reality opens up ASP.NET to a radical new gathering of people of engineers and originators. The customary gathering of people for ASP.NET is proficient engineers working in a company. Corporate clients are welded to their Windows machines.Difference 2 – I cherish ASP.NET Web Forms. I've burned through hundreds – if not thousands – of hours of my life building Web Forms applications. In any case, it is at long last time to state farewell. ASP.NET Web Forms is not a portion of ASP.NET 5. You can keep on building Web Forms applications in Visual Studio 2015 by focusing on the .NET 4.6 system. In any case, Web Forms applications can't exploit any of the cool new elements of ASP.NET 5 depicted in this rundown. On the off chance that you would prefer not to be abandoned as history walks forward then it is at last time for you to revise your Web Forms application into ASP.NET MVC.Difference 3 – It is additionally time to state farewell to Visual Basic. ASP.NET 5 just backings C# and Visual Basic is deserted. My trust is that this change won't be excessively agonizing. I trust that there are just two individuals in the whole world who are building MVC applications in Visual Basic. It is the ideal opportunity for both of you to stop it. There are great programmed converters for going from Visual Basic to C#:Difference 4 – In past renditions of ASP.NET MVC, MVC controllers were not quite the same as Web API controllers. A MVC controller utilized the System.Web.MVC.Controller base class and a Web API controller utilized the System.Web.Http.ApiController base class. In MVC 6, there is one and just a single Controller class that is the base class for both MVC and Web API controllers. There is just the Microsoft.AspNet.Mvc.Controller class.Difference 5 – Farewell Visual Studio Unit Testing Framework and hi xUnit.net! In past adaptations of ASP.NET MVC, the default testing system was the Visual Studio Unit Testing Framework (here and there called mstest). This system utilizes the [TestClass] and [TestMethod] credits to depict a unit test:
To know more read this article Top 10 Changes in ASP.NET 5 and MVC 6
and for latest updates visit this site thank you. CRB Tech - Latest techno updates
It got renamed to ASP.NET core.. it got released 2 days ago:
https://blogs.msdn.microsoft.com/webdev/2016/06/27/announcing-asp-net-core-1-0/
Initially, I thought the changes would be small because the code looks similar but converting my relatively simple project turned into a mess. I was using RC2 hopefully the release version is better. Tons of breaking changes, conflicting libraries, and general flakiness. The only way I could even get it partially working was disabling security because it did not support many of the security models used in old MVC... I abandoned my attempt. I think the priority for this release was multi platform support, and some steps backwards were taken. The approach looks much better but I'm not sure all the kinks are worked out yet.