SiteMapPath .Net component works fine on .Net environment. But it seems not on .Net Core.
For e.g., if the https://www.c-sharpcorner.com/UploadFile/2f59d0/implementing-sitemap-in-Asp-Net/ is developed choosing .Net Core, the breadcrumps as expected do not show up.
But I couldn't find any official doc from Microsoft on that. Does any one know.
Thank you.
Related
Is there a solution currently help convert the targeted member "System.Windows.Forms.Control" in windows CE to .Net Core?
Assembly: "Device.WindowsCE.Forms.NET46"
Id' rather not have to rewrite all the areas when I'm using the assembly if there is a conversion tool or something that can help this change become a lot easier.
There is nothing currently that exists to do this functionality, we will be doing it ourselves manually.
I have a Data Access Layer solution built in Visual Studio 2010. It uses Entity Data Model (.edmx files) to create object models of the data.
It is built with .Net 3.5 framework so I assume this is also version 3.5 of Entity Framework?
We use a number of TVFs to return datasets and unfortunately EF 3.5 does not provide access to TVFs. So we have has to build tsql views that call those TVFs.
Is it possible to upgrade this solution to EF 6 and use TVFs? What are the steps involved?
Microsoft has release a guide to do. You find it here:
https://msdn.microsoft.com/en-us/data/upgradeef6.aspx
It involves getting the latest assemblies and do some modifications in order to run. It seems upgrading from an older version is a little harder than from a new version.
I am creating a .net library in Visual Studio 2015 with the following aims:-
Support for .net 2, 3.5, 4 and 4.5+
PCL Support (.net 4.5+)
No extra dependencies apart from Json.net
Ideally the .net 4.5+ version of the library would make use of async, and include methods that return Task etc
Now there seems to be many different ways of supporting what I want to do, especially with the Visual Studio 2015/project.json release but what is a good approach starting from scratch today?
My library is relatively simple, so as much as I want to re-use code I don't want to compromise the .net 4.5 version.
What would be a sensible project structure, that would mean I could take advantage of the latest .net framework, but still build in support for older frameworks.
With Beta8 of the WebDev tooling you are able to also target net2, net35, net40, net45, ...
Your library differences you might use #ifdef flags in your code to hide certain methods in certain builds.
I've been looking at the new Entity Framework 4 Code Only features, and I really like them. But I'm having a hard time finding good resource on the feature. Everything seems to be spread around blongs here and there, so this make me wonder if it's ready to be used for a serious project?
What do you think? Is it ready for production use or should I use the more traditional approach (EDMX designer, POCO objects)?
Also, I would like to know if there are any features that Code Only does not support yet, compared to the EDMX designer?
What do you think about the Code Only feature? Is it "mature" yet?
Thank you.
It depends when your project should be ready. Code First (Code Only) is only in CTP3 without go-live license. As I've read, there is no exact timeframe for the Feature Pack Where is EntityConfiguration in EF4 VS 2010 RTM? and it will be published when it will be ready (no release date). According to the blog of EF team it will be available in the next framework release.
Code First is still under active
development and will have some
breaking changes so there is no
go-live licence at this time.
Link
Code First = Code Only
In my projects I went with EF + POCO for now.
If anyone is still looking for an answer to this, Entity Framework V4.1 which has the "Code first" feature has been RTW (released to web) for production use since a month and a half now.
You need .Net 4.0 RTM in order to install it. Once you have that installed, you can download the stand-alone installer for EF4.1 from here.
I have an application I want to upgrade to .NET 4, but I have a couple 3rd party assemblies that reference the .NET 2 BCL.
I seem to remember reading something that says they should play nice, but I can't find any documentation on the subject. ( I think my question posed to Google is just too broad, with not enough .Net 4 material out there yet )
Can anyone help me find documentation on what will happen in this case?
If I'm reading Scott Guthrie's post, Multi-Targeting Support (VS 2010 and .NET 4 Series), correctly then that will work fine.
Of Interest?: .NET 4.0 project reference 2.0 assembly
The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
I wanted to reference StructureMap in one of my class libraries. Orginally it was created by VS2010 to use the .NET 4 client profile. Turns out, I had to changed this to the full .NET 4 framework, otherwise structuremap would not be recognized.