Creating an ASP.NET MVC app from scratch - asp.net

So far i've only been using webforms. But me and my friend would like to try out the MVC architecture. Some questions:
Is there any downside with the free version of visual studio VS professional? I can get the professional version from work but is it worth the effort?
I would like to use Entity Framework and the latest version of MVC + the razor view engine. Does this need to be downloaded separatly?
As far as versioning is concerned; is tortoise SVN suitable for a small project on 2 persons?
Any help is appreciated, thanks.

SVN is ok as a repository in my experience. If you are using Visual Studio there is a decent plugin so you can use it from within the IDE, rather than from within Windows. If I am using SVN, it is what I use! More details here.
MVC3 can be downloaded here
Entity Framework can be installed via Nuget (PM> Install-Package EntityFramework ) or a quick google will show the download locations (I think there is version 4.3 and a CTP of version 5)

Free version will work, not sure if there are any differences.
Yes you need to download it seperately
Why wouldn;t it be?

Not that I know of. It's a good way to start. I know earlier versions didn't allow plugins but not sure about the latest versions.
EF will come with the .NET SDK (VS) so no need there. You can get MVC3 from the Web Platform Installer (http://www.asp.net/mvc/mvc3)
I use Tortoise SVN on a team of 4 people with no issues at all. Just make sure you all know good rules for source control management.

Related

How to properly change target framework to .NET 4.0

I built an application with target framework .NET 4.6 using MVC 5 and Entity Framework 6 using Visual Studio 2017 on my Windows 7 machine. I'm now being told that I should have built the application to target .NET 4.0 because the production environment only has 4.0 installed. So I changed the target framework to 4.0 but now the application will not build on my machine.
I'm guessing I also need to downgrade MVC and EF. How is the proper way of doing this?
And which versions of MVC and EF should I install?
Do I need to make any manual changes to web.config?
There is no "proper" way, you have 3 options, in my favorite order:
Update the server and install the latest .net version. (at the time .net 4.6). Make sure used libraries are up to date and not end of life.
Start over in a new project and make sure you target version 4.0: you can copy most of your source files. You'll probably get some compiler errors, but usually they are easily fixed. This way you'll have the benefit that the used template matches the framework and packages version(s).
Re-target the used framework in the project properties and replace the packages which are installed and hope for the best (sometimes you need other packages). Hopefully you used the package manager to install those packages. Maybe the update-packages command helps, but be sure to backup your project first. Some packages become obsolete after time, some are renamed. This is what will cause issues. Also, some of the Methods/API calls will be different, so some rework will be needed.
As for the rest of your questions:
I'm guessing I also need to downgrade MVC and EF. How is the proper way of doing this?
Use the nuget package manager
And which versions of MVC and EF should I install?
The nuget package manager will fix this for you.
Do I need to make any manual changes to web.config?
Sometimes: yes.

Installing MVC on asp.net Core in visual Studio 2015

I created an empty ASP.NET 5 to work with .NET Core. I am trying to add MVC package to the application but I am receiving an Error that the Versions are not compatible, although I tried lots of MVC versions.
Anyone has an idea about the problem? thank you!
You need Nuget packages in the Microsoft.AspNetCore.Mvc namespace. You're currently trying to install Microsoft.AspNet.Mvc 5.2.3, which is the traditional MVC package and only works with full .NET.
If you're working with .NET Core you should be using Microsoft.AspNetCore.* packages. (Microsoft.AspNet.* packages target the full .NET framework.)
Your screenshot shows a dependency on DNX. You do realize that's a pre-release technology? I don't mean to be rude but I'm curious as to why you would be targeting the pre-release framework rather than RTM (which has been available for several months).
If you do want to work with the prerelease bits, you may need to tweak your NuGet feeds to be able to see the appropriate .NET Core packages (I definitely had to do this when working with .NET Core betas).

rebuilding subsonic 2.2

I haven't programmed for 2 years so please be gentle in your answers. I'm returning to an old asp.net 2.0 project i wrote a few years ago using subsonic. I can't work out how i got subsonic working in this asp.net project as it is an old version (2.1) and the documentation for 2.x doesn't ring any bells with how I used to have to build the code. Anyhow, I have downloaded subsonic 2.2 and have managed to get that to work so I will use this in the website. However I have seen various webpages saying that subsonic 2.2 requires a very specific version of the mysql data connector (5.2.3 i think) and that I should rebuild subsonic 2.2 with a newer version of the connector.
Questions: is this necessary? If so why? Can't i just use version 5.2.3 of the connector in my website or does asp.net override it with its own version (by the way i generate my DAL in a separate class project and not the website itself)? Can i prevent this from happening? If this is necessary, how do i do it as I really can't remember. Would i just create a new project, add the subsonic source files and the appropriate connector dll and rebuild the subsonic dll or is it more involved than that? Is subsonic 2.2 still supported or am I flogging a dead horse trying to use it?
thanks a lot
As you generated your DAL in a separate class project then you should be able use whatever version of the MySQL adapter .dll you like in your web project.
The other option is to use SubCommander program to generate the classes.
I'd strongly advise grabbing the latest version 2.x from https://github.com/subsonic/SubSonic-2.0 and compiling your own. Failing that if the project isn't too large then maybe look at migrating away? SubSonic was a great tool at the time but there are much better options available now.

how to migrate from .NET1.1 to .NET3.5 version

currently iam using .NET1.1 version in next few days i will be migrating this .NET1.1 application to .NET3.5 version...so my question is how to migrate this .NET1.1 to .NET3.5..?
How to migrate this & what precuations i need to take...? plz help
If you are using Visual Studio for your development there is an upgrade feature that takes care of quite a few things.
Here is an article on the topci that might help you. link
As #Development4.0 suggested, you could open the 1.1 sln file in VS2008 and go through the wizards. If you have multiple projects (like Web Projects, Class Library etc), then I would suggest a step-by-step approach. There will be breaking changes for sure, but I think would be minimal.

Do I need to purchase a license when I will be creating a website/webapp using mono?

I used asp.net in a project in an old company. The vs was licensed etc. Right now, I am planning to use mono since my new company is using linux based stuff and I heard that mono uses the .net framework etc. I just want to know if I need to purchase anything or is it ok to create a webapp using mono?
You can create a webapp using mono wihtout buying anything, of course. You only buy from Microsoft the license of Visual Studio, not the .Net compiler nor the Framework.
#SoMoS has the right answer. If you want more detail, and a better explanation of the patent situation, check out the Mono Licensing page.

Resources