Is there any difference in functionality between installing umbraco via the webmatrix installer compared to installing the nuget package?
You will get the same install of Umbraco, so no there's no difference with regards to Umbraco. Of course there's a difference in the way you install it and maintain it. It's up to you to make a choice, whatever you're most comfortable with.
Note that when you do install through webmatrix it is then harder to work with Umbraco through Visual Studio (in case you prefer using VS).
Installation documentation available here: https://our.umbraco.org/documentation/Getting-Started/Setup/Install/
Related
I have upgraded the server to ASP.MVC 5.
In Control Panel in Installed Programes, I found:
ASP.NET MVC 2
ASP.NET MVC 3
ASP.NET MVC 4
ASP.NET MVC 4 Runtime
It is safe to uninstall all of this older ASP.NET MVC? There is no ASP.NET MVC 5 in list. It is because it was installed via Nuget?
MVC is bin deployable - meaning that you don't have to install it at all if you don't want to. Earlier versions of MVC were easier to run if you had installed them, so this is probably why you have installations.
By default, anything you fetch from nuget is bin deployed (as it isn't installed on your machine, the files are added to your project).
You can safely remove any installed MVC packages - and if you do have projects that depend upon them, you can install MVC in any project using nuget, and specifying a version (back to version 3) - for example:
Install-Package Microsoft.AspNet.Mvc -Version 3.0.50813.1
Install-Package Microsoft.AspNet.Mvc -Version 4.0.40804
Install-Package Microsoft.AspNet.Mvc -Version 5.2.0
There are no dependencies of newer MVC versions on older ones, they are simply a newer version of the set of dlls, so there should be no issue removing older versions.
There are no dependencies of newer MVC versions on older ones, they are simply a newer version of the set of dlls, so there should be no issue removing older versions.
Are you sure???
NuGet decided to upgrade an MVC 4 to 5 box and it hosed the solution. Right now, I have this problem:
access method 'System.Web.Http.HttpConfiguration.DefaultFormatters()' failed
But, any solution found on the web right now has not worked.
It seems Microsoft is back to the ol' marketing tricks, bundling crap galore and creating an evangelizing environment where those using their technologies spend an inordinate amount of time on THEIR technologies, not the end solutions. I'm so frickin' mad that if my solution doesn't start working soon I'm tossing Asp.Net MVC after using it for four version with ZERO problems like this and going node.js.
I have recently installed the Aptana plugin for Eclipse as I wish to learn Ruby and Ruby on Rails, it doesn't seem to have changed anything. Usually when I install a plugin of the sort, there will be new project types under the "New Project" menu, but none appeared. I checked tutorials online and they suggest that there should be new project types as seen in the image below, taken from a tutorial.
Instead, I see the same options I did before.
I wondered if the plugin didn't install, but when I try to install it again, It says it's already installed. I am using Eclipse Juno Service Release 2 with a 64-bit Windows 7 operating system and the version of the plugin from the URL given on the Aptana website (http://download.aptana.com/studio3/plugin/install). Any help would be much appreciated.
I don't know why that's happening. Here's a suggestion for how to get around it.
You might be better off installing and running the standalone Aptana Studio product. It would be a separate installation on your desktop, and thus wouldn't have the same settings as any Eclipse installation you already had, and would be more space on your hard drive. But probably there isn't much you would share between Ruby/Rails development and other development, and it's not that much space.
I've done it both ways - installed Aptana into an Eclipse I've already got, and installed the standalone version - and now I would only do standalone.
I don't know what was wrong in the first place, but after I installed the Aptana plugin, I installed the PyDev plugin. I think this removed the Aptana plugin because of conflicting dependencies (I don't know why it wouldn't tell me, though). I tried installing the Aptana plugin again and it told me there was a conflicting dependency with the PyDev plugin, so I uninstalled it and reinstalled the Aptana plugin. It works now.
I am using EF 4.0, at the time I am writing these lines I heard that EF 4.1 update 1 has been released and EF 4.2 is in beta. From wikipedia
A refresh of version 4.1 named Entity Framework 4.1 Update 1, was
released on July 25, 2011. It includes bug fixes and new supported
types.
But I only found a link of Version 4.1.10311.0 from Microsoft which date published is 3/21/2011. So I wonder if version 4.1.10311.0 is the latest release so far. If it's not, where can I download the latest release ?
ps : For some reasons I can't use live update, I need to download package to install manually.
From Arthur Vickers:
What if I can’t use NuGet? What if you can’t connect to the Internet
from your development machine. Or what if you are not allowed to
install NuGet on your machine. Don’t worry; all is not lost.
First you need to get the NuGet package. For this you do need to be
able to connect to the Internet from some machine—but it doesn’t have
to be your development machine. You’re reading this so presumably
you’re not completely off-the-grid. :-)
You can get the package by using NuGet in Visual Studio on a machine
connected to the Internet in the normal way—just install the package
you want into a dummy project. After installing the package you can
find the .nupkg file either in the dummy project folder or by browsing
the Package Cache from the Package Manager Settings menu option.
You can also get the package without Visual Studio by using NuGet.exe.
If you are able to install NuGet on your development machine then do
so and setup a local feed. This may sound daunting but it’s really
easy. Copy the .nupkg file to your local feed and then use NuGet to
install it in the normal way—with no connection to the Internet
required.
If you can’t install NuGet on your development machine then take the
.nupkg file and rename it to .zip—yep, it’s a zip file. You can now
extract EntityFramework.dll from the zip file and use it as you would
any other assembly. Note that you will not get any of the automatic
project-level integration I mentioned above, so you may have to do
more manual configuration of your project.
If you are using EFv4.0 you mostly don't need EFv4.1 or EFv4.2. Those versions bring new type of mapping (code first / fluent) and new DbContext API which can be used instead of ObjectContext API. So unless you want to start a new project with those "new" features or completely migrate your existing project you don't need it. Real new functionality for you will be included in .NET 4.5. DbContext API and code first is shipped only as NuGet package since EFv4.2.
use the package-manager in VS2010 to install
Tools + Library Package Manager + Nuget package manager
EF 4.2 has just been released: http://blogs.msdn.com/b/adonet/archive/2011/11/01/ef-4-2-released.aspx
This is a minor update over 4.1.
The runtime components are available via NuGet. The designer etc. updates for VS are a separate install.
More and more gems I run into requires building "native extensive", such as RedCloth. Are there tools that are open-source or free that is sufficient to do that? I heard MS Visual Studio also has a free version. Will that be enough to build native extensions?
If you installed Ruby with the RubyInstaller (as you should), then the DevKit has everything you need.
If you use the obsolete MSVC6 builds, then you need to install Microsoft Visual C++ 6.0, because newer versions of MSVC are incompatible. Good luck finding that, though, MSVC6 isn't even from this millenium.
I need to know whether to work with sharepoint templates I have to have visual studio installed on the server?
No. Developers create solution packages during development and you deploy those solution packages to the server(s) using the Solutions Framework.
See http://msdn.microsoft.com/en-us/library/aa544500.aspx