Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I have a ASP.NET Framework 4.0 WebForms project running on several Windows servers. I wonder about the goals I should achieve to be able to host the project under Linux. Let us suppose I refactor the project and upgrade the version of the Framework to 4.5 or 4.6. If we assume that I do not have Windows-specific code in my project either because I never had such a code, or because I refactored it to not assume Windows-specific properties. My question is: what are the known mainstream .NET components that will break under Linux?
No matter how well you assert it on Windows, running the web app on Linux and Mono can reveal what does break.
This question therefore is too broad. I blogged about running ASP.NET 4.x web app on Mono,
Jexus Web Server and ASP.NET Cross Platform
I was invited by Mingzhi Yi to give a talk at Jiaodong Developer Conference 2015 on 12 Dec. It was about my opinions on Jexus and ASP.NET cross …
https://blog.lextudio.com/2015/12/jexus-web-server-and-asp-net-cross-platform/
You should note that .NET 4.6 might not be well supported on Mono, as it evolves slower than .NET.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I have gone through .NET 5 features and looks like everything is understandable but I have few points. Can anyone please correct my points that are listed below?
DOT NET 5 has a single CLR for both Framework and Core
DOT NET Standard is the way to share a library between the .NET framework and .NET core
As per the documentation, the .NET 5 is the next version of .NET Core. If we install .NET 5 on Linux, we can't create and run framework related projects on Linux because still, they are windows specific applications.
I think the backword compatibility from .NET 5/ .NET x to .NET Core 3.1/ .NET Core 2.1 will be possible if there are no breakage changes.
For .NET core 3.1, we can install the runtime and run the already built application. Is it the same case with .NET 5. we can just install the .NET runtime and run the .NET 5(Framework and Core) applications.
No, Framework and Core/5.0 have different CLRs.
Yes, .NET standard is effectively the bridge between Framework and Core/5.0. That said, Standard is effectively end-of-life (final version is 2.1) as Microsoft no longer wishes to support Framework going forward.
Yes. Framework applications are and always will be restricted to Windows only.
Yes.
No, you have never been able to execute Framework apps via a Core runtime or vice versa. You need the matching runtime for the type of application you are executing.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have a project in .net framework, now I want to convert it to .netcore. what will be steps for doing this migration
From MS Documentation
Retarget all projects you wish to port to target .NET Framework 4.7.2 or higher.
Use the .NET Portability Analyzer to analyze your assemblies and see if they're portable to .NET Core.
Install the .NET API analyzer into your projects to identify APIs that throw PlatformNotSupportedException on some platforms and some other potential compatibility issues.
Convert all of your packages.config dependencies to the PackageReference format with the conversion tool in Visual Studio.
Create new projects for .NET Core and copy over source files, or attempt to convert your existing project file with a tool.
Port your test code.
https://learn.microsoft.com/en-us/dotnet/core/porting/
Enjoy reading... ;-)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I am going to deploy 2 ASP.NET Core 2.2 web applications onto an IIS environment. I was wondering if there were any options in the market to facilitate automatic deployment?
For my previous application that was in PHP, I could use a service called Deploybot that took my code from GitHub and pushed it onto a server. I really enjoyed that one because setup was straightforward and I could easily rollback or deploy new code due to it being tied to my GitHub branch.
Are there any similar tools I can use for .NET Core? So far I've seen Jenkins as a recommendation. Are there any other services that perform similarly to Deploybot but for .NET Core applications?
My current planned method is to use WebDeploy and publish the applications straight from Visual Studio. But the problem is that it won't have a proper link to GitHub.
Azure DevOps, Jenkins, TeamCity, TravisCI, AppVeyor. These are just a few of the tools that you can use to facilitate CD (Continuous Deployment) from sources like GitHub, BitBucket, git, tfs, etc.
I've used both AzureDevOps and AppVeyor in the past, and found both of them to be really good at what they do. Although, I've only used Azure DevOps in a professional setting and AppVeyor for personal projects.
I've written about how to set up AppVeyor with .NET Core in the past - here is a link to that article.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have a big website that developed with MVC5 and I wanted to convert it to .Net core.
Everything works great but when I wanted to add my references to .Net core edition of my project I saw that .net core just accepts References of .net core type or some references that can be install from nuget.
I decided to convert my DLL References to .Net core dll types and because of this create a new .Net core class library but when i click to add some references to this class library like Syste.Drawing , I saw there is nothings on references list.
After some searching on google I founded some posts like
Server-side graphics in ASP.NET Core
Manipulating images with .NET Core
....
After encountering with this problem I was thinking may be it's possible I encounter with a problem like this who I can not handle it in .Net core and I should stand by until Microsoft releases a more complete edition of .net core.
Now the question is that is .net core stable to start a real project/product or
not?
As always the decision depends on what do you want to achieve.
ASP.NET Core is a brand new web framework with cross plattform and performance in mind. In these days "real projects" are developed based on the version 1.0. The code for 1.0 is released and supported by Microsoft - so this is production ready. The tooling itsself is in preview (Visual Studio integration).
If cross plattform is not a major requirement for you right now, then you can choose Windows as plattform for your application and you can access the whole .NET Framework including the many, many libraries of the .net world. Later on you can swap to .NET Core libraries by the time more and more libraries will support .net Core.
As it is a version 1.0 there are typical pitfalls compared to a long lived web framework like ASP.NET. Documentation is in progress or features that you might miss these days (like SignalR) can be a major no go for you.
So you have to investigate to gain the information specific to your requirements. ASP.NET Core is production ready starting point especially if you plan a new product from scratch.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm a diehard mac lover but my day to day work is shifting towards the .net stack, specifically c#, asp.net mvc, entity framework, multiple project class libraries, ms test, sql server, deployment to azure.
In light of the recent cross platform advancements in .net, what issues (if any) would I face now and later on as I get deeper into development? Is anyone else doing this?
I've installed VSCode (https://code.visualstudio.com) and am able to build and run an asp.net mvc web app using coreclr. That seems to work very well and is closer to the web development experience I'm used to on a mac. I understand I also get vs.net style debugging with VSCode but I've yet to test that.
SQL Server I realise will be a problem, I'm considering either running it in a VM or using a cloud based dev instance.
I've also trialed running full vs.net in a VM but on my 13" MBP i5 8GB it gets a tiny bit sluggish at times under VMWare Fusion, so not ideal. VSCode also gives me a dev experience much closer to what I've been doing previously from my mac (simple text editor, terminal etc) so I prefer that anyway.
So, can I do this? is cross platform .net ready for mid sized asp.net apps? what problems may I run into? I appreciate any feedback.
Since you've already installed VS Code on your Mac, you already know that you can work on ASP.NET projects natively on your Mac. Just keep in mind you can run the cross-platform .NET Core 5 on your Mac, but not the full .NET Framework. So, if you need to work on any projects that need the full framework (such as .NET 4.x), you will need to use Windows. It doesn't matter if it's small, midsized or large enterprise apps.
As you suggested, you can run Windows on your Mac. But instead of VMWare, I would suggest Parallels instead. Running Windows on your Mac will allow you to run the full Visual Studio with the full .NET framework if that's what you need. It would also let you run SQL Server on Windows inside your Mac.
Hope that helps! :)