I have created a Module(Portal). I am going to publish it. I just don't know which version it can support. The previous versions and future versions. I am just curious above this all specially in case of .DLLs.
Please suggest me.
Development system
1- Visual Studio 2015
2- DotnetNuke 7
DLLs
It will all depend on what version of the DotNetNuke.DLLs you compile your module against.
Typically if you compile against a version, say 07.00.01, the module will run on that version AND any NEWER version of DNN.
There are some cases where there are breaking changes for modules on upgrade of the DNN version, but they are pretty few and far between.
Related
I was looking for some NuGet updates about my project libraries. I see that there are a lot of Microsoft libraries update to v5.0.0.
Based on my knowledge I think these are new dependencies released with .Net 5.0 and I'm not sure that I can update these libraries to latest version using .Net Core 3.1 project.
Can I update to v5.0.0 libraries even if I'm using/building a .Net Core 3.1 project?
Unfortunately, you cannot update many of these newest Nuget packages to 5.0. The reason being is that the newest Nuget package versions are written primarily for .NET 5, and often times Nuget Package Manager will even prevent you from installing them since there are differences in the APIs. With that said, there may be a few spots where it will allow the installation, but I wouldn't recommend it if you plan to keep the application on .NET Core 3.1. Most likely it could cause some inconsistencies that would be hard to debug. Proceed with caution, or upgrade your projects to .NET 5.
I just finished the same. I had 3.1 core application with a lot of 3.1 and NET Standard2.0 libraries projects and just updated all these libraries to the version 5. All libraries were working ok, I could compile them. But I couldn't compile my main Web application. It started to give some strange errors that some staff needs .net5. Maybe it could be fixed but I didn't see much sense to waste my time since in any case I was planning to move to net5 in a couple of days. So I just decided to move to net5 immediately. I had installed net 5.0 SDK and change target framework of my application to net5.0. Now everything is working fine and I am happy with my net5.0 application. I have some Net 4.8 projects that use the same common libraries that I am using for Net Core. So these common libraries are targeted to netstandard2.0. and can't change them to Net5. Now all these Standard2.0 projects still work with my net5.0 web application without any problem. Since I didn't have any problems with my previous version 3.1.9 I DON'T RECOMEND to update libraries to 5.0 if YOU DON'T PLAN to move your application to Net5.0. You can get more problems after this then you can gain from this update.
You should report such (VS for Mac and VS for Windows) as product defects to Microsoft, as many of the new 5.0 packages are targeting net5 solely, and not applicable to netcoreapp3.1.
Try to use outdated tool to check package updates, which is much more reliable,
https://github.com/dotnet-outdated/dotnet-outdated
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.
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.
On specflow's own instalation guide it says that the only way to install it is using the .msi installer and most of the tutorials I've read on the subject tell me to download and install said file but when I search on the nuget package manager I find there's also an available package for specflow.
The difference is in the tooling. With the MSI you get full item template, syntax coloring and intellisense support in the IDE where as with the NuGet you just get the code generation and runtime support. So I'd say 9 times out of 10 if you're going to be doing any serious work with it you're going to want the MSI for those rich features.
At this point they really should be offering it as a Visual Studio Extension for a lot more integrated install experience using VS Extension Manager.
I want to use Aptana Studio 3 Beta for all my Ruby developments. I am planning to write a Windows appl. using FxRuby framework, but how to integrate this framework with Aptana Studio 3?
I'm not 100% sure I understand what exactly you're looking for here. Studio 3 will index your ruby core, std lib and gems installed on whatever version fo Ruby is on your PATH. It uses that index to generate code assist. As long as you have the fxRuby libraries built and installed into your system, we should pick up the ruby API and offer code assist for you.
Here's the relevants ection of fxRuby's wiki on building their library on windows: https://github.com/lylejohnson/fxruby/wiki/Setting-Up-a-Windows-Build-Environment
I will say a word of caution: installing, building and generally dealing with Ruby binaries on Windows is a difficult task unless you're comfortable with MinGW.