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 4 years ago.
Improve this question
We have few classic ASP web applications which are to be converted to ASP.NET Core. Few questions:
1) Are there any tools which can help in migration
2) I have Windows server 2016 - what version of Visual studio , edition and framework is required to be installed on the server ?
3) Are there any other software / NuGet packages which are required as pre-requisite ?
4) What should be the approach taken for such migrations ?
Thanks
ASP.NET and ASP.NET Core, despite both having "ASP.NET" in their names are fundamentally different things down to their core, no pun intended. As such, no, there is no "tool" to migrate for you, because it basically requires a rewrite. You should not look at moving to ASP.NET Core as a "migration". You are creating a brand new application. The way you structured your previous app, how you chose to do things, the very architecture itself, will all need to be re-evaluated, just as if you were starting from scratch, because you essentially are.
I'm actually in the middle of such a "migration" myself, but I've taken the opportunity to move to a microservices architecture. As such, I'm essentially just breaking off pieces of the old application and replacing them with microservices. This makes it relatively easy and straight-forward to start using ASP.NET Core while at the same time keeping your existing ASP.NET application working, limiting the scope of the changes required. Eventually, once all the core functionality is spun off, all you'll essentially have left is the UI, which is a rather simple replacement overall.
As far as tooling, you must have Visual Studio 2017, edition does not matter. 2015 can only work with up to .NET Core 1.1, and not well even then. 2019 will be a better option once it's generally available. Basically, just use whatever the latest GA version is always. There's some benefit with the Enterprise edition as you get things like Live Unit Testing with that, but you can develop full ASP.NET Core apps on even the free Community edition, just without all the Visual Studio extra bells and whistles you get for paying for higher versions.
NuGet packages are specific to your app, so you'll decide on those as you build. As far as other software goes, if you want to take the same microservices architecture approach, you'll want to have Docker for Windows installed. Generally, you'll of course also need the .NET Core SDK you plan to target installed, as well.
Related
I wanted to host my .net core API in Go Daddy Linux Server and also .net Core Web APP is there any possibility to do that. Also I have seen lots of tutorials to make that happen in Linux server which is for cloud but doesnt work the same scenario for any another on premises server.
If anyone have this experience or can only suggest that if there is possibility for hosting in the go daddy linux server it will be really helpful
It seems that you need to ask them whether they have support .net core on their Linux hosting package. I ever worked with them in the past 8 years ago, I didn't like their support, but I don't know now, maybe they improve better. If you want to use .net core on Linux, Digital Ocean can be good option. I also .net user here but I always use Windows to deploy my .net. From Classic ASP until newest .net core project, I always use Windows Server.
I need to develop an application for my distributed computing class, with one central server and multiple graphical clients. I was thinking of trying WCF for this, since I am already familiar with making .NET standalone desktop applications using Windows Forms or WPF.
Since I have never worked with WCF before, I am trying to follow a tutorial posted on MSDN, which has defining a service contract as its first major step.* Part of this involves creating a WCF Service Library project, which is supposed to be available as a template under the language of my choice (I am going to use C# here). However, I do not see this project template listed as an option in the new project dialog, and looking for WCF in the search bar returns no results.
How can I make this project template available for use in Visual Studio 2017?
* It should probably be noted that the tutorial mentions that it is written with Visual Studio 2012 in mind. Has anything changed since then that I should be aware of as far as the tutorial is concerned?
Open the installer, choose Individual Components and scroll down to Development Activities. Check the WCF checkbox:
I ended up re-running the Visual Studio Installer to modify my current setup. WCF is not explicitly listed anywhere, but I figured it might have been included as part of the .NET Core or ASP.NET workloads (which were not marked for installation the first time around). After adding these workloads to my installation and restarting Visual Studio 2017, I can now see the WCF project templates listed under C#.
We've been asked to look at SharePoint 2010 Standard (we currently have a small intranet on SP2007) with an aim to building a number of custom workflow solutions.
I don't have much experience of SP2010, but from a period of learning/testing it seems to be a very cumbersome system more tailored to allowing individuals/teams to create their own web sites for a specific purpose?
I have also seen some blogs on WF4 - which I have even less experience of! Can WF4 be used "stand alone" or does it require SP2010?
The workflows will range from very basic to reasonably complex based upon variables. e.g. "Route to next person in chain", "route to team based on a value(s)".
So my question is: Could someone give me any assistance in deciding which route to attempt for building workflows? I'm not even sure of the questions to ask of each of them! I appreciate this is subjective, but I'm sure there are people out there who have experience of both?
My experience is in C#.Net/MVC and WCF - the overhead of simply getting an SP2010 Dev environment setup and configured has already made me wary of SP2010!
I can´t tell you much about SharePoint other than that SharePoint 2010 still uses WF3 for its workflow engine. In SP2013 they upgraded to WF4 so if you are looking to run WF4 style workflows you will need to use that instead.
Windows Workflow Foundation is independent of SharePoint. You can create your own Workflow host and Persistence layer. APress had a great book, Foundations of WF which served as a great introduction to Workflow in .net 3.5.
SharePoint 2010 is based on .net 3.5 SP1 and uses the old/original Workflow Engine. It implements its own host and persistence, so it's quite its own beast. There is a wealth of information available for Workflow in SP2007 and SP2010, which is good because the list of caveats, exceptions and "You need to know this, or it'll bite you" cases. In addition, SharePoint 2010 allows workflows to be created in multiple ways: Through Visual Studio (Like a "real" WF Project), through SharePoint Designer and through Visio (the latter two being limited).
WF4 is a new Workflow Engine that Microsoft introduced in .net 4.0. It is not supported in SharePoint 2010, but the next version - SharePoint 2013 - is based on .net 4.5 and should in theory offer support for WF4. I have not verified this though.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
What is the difference between
project 2010 and project server 2010
specially integration with sharepoint 2010 ?
With Project 2010 Standard you can:
manage local projects
manage shared projects stored on network shares
manage resources stored inside of a project or manage resources stored in a resource pool file
link local and shared projects
if ODBC (database) is used to store project plans - you can build reports from the projects' data
Project 2010 Pro is Project 2010 standard + ability to work with Project Server
With Project Server 2010 you can all you can do with Project 2010 Standard + :
manage resources, security, views, templates, custom fields with lookups from one place
assign workflows to project plans
you get one more interface to your project plans: Project Web application. It costs slightly cheaper than Project: about $150 for PWA and $1500 for Project Pro.
your people can report their timesheets and progress directly to projects
you are getting better reports: Project Server includes BI reporting
API to work with projects which is much better than COM provided by desktop MS Project
Export tasks to SharePoint and Outlook (Exchange Server)
People believe that Project Server is Enterprise solution and it gives them some super enterprise functions they were never had with just desktop MS Project.
Practically you can implement the most of the Project Server features using combination of other technologies, but sometimes it is better to get something already done than reinvent a wheel.
I am currently in the early stages of developing a couple web applications, I have not written any code yet as I am still just gathering requirements and scoping things out. I want to target ASP.Net 4.0 winforms as the platform for these apps but I want to make sure there are no glaring issues with this new version before I commit.
I understand that if I was porting an existing app from 2.0, 3.5 to 4.0 there may be issues but I am starting from scratch on these projects and plan to write these apps to support the new features of 4.0.
Should I wait for the first service pack to come out? Just seems like more work to start with 3.5 now only to go back through and tweak things for 4.0 in just a few months or even before I finish the app.
Our servers are Win 2K3 with IIS6 and MS SQL 2000, Should I expect any problems with VS 2010 and MS SQL 2000 in regards to Linq to SQL and EF?
Do it. I do the same at the moment. SQL 2000, though - is out of support. Even the bank I am sitting in at the moment is now replacing it with 2005 / 2008. I would seriously consider upgrades.
Web application? Using SPLA (only legal licensing for service providers - purchased licenses are not legal here) you get 2008R2 and SQL 2008 R2 anyway.