Nuget Package 'UmbracoCms.8.0.0-alpha.58.1540' is installed successfully.
when building (Ctrl+f5 from vs 2017) the successfully installed nuget package..
I get
Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request.
Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Umbraco.Web.UmbracoApplication'.
Source Error:
Line 1: <%@ Application Inherits="Umbraco.Web.UmbracoApplication" Language="C#" %>
Source File: /global.asax Line: 1
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3282.0
It looks like all the required umbraco dlls aren't being propagated into the bin folder (they don't appear n the solution references either), are there dependencies missing in the nuget package?
I do have a v8 up and running via cloning the whole source from github.. but just wanted a release binary to play with and though nuget would be it?
Not sure what more we can do @Pedro, we already require .NET 4.7.2 : Maybe we can make it more strict? If you know how to, I would love to hear about it:
Aha, here's a simple thing we can do, if we force NuGet to have to be at least version 4.6.0 then people will need to update to a pretty recent VS version first, that should help a lot.
Just to confirm, on a clean VM (Win 10 1809) with VS2017 15.9.7 and no 4.7.2 developer pack installed, Umbraco 8 does install correctly. It's going to be difficult to figure out what exactly was wrong on your machine but I guess a side-effect of installing the developer pack is that "something" got fixed.
As an FYI on this... depending on the state of your machine and when things were installed you "may or may not" have had the "dev pack" installed when VS installed.
If your machine had VS2007 on before you upgraded Win 10 to the creators edition then the Dev Pack for 4.7.2 wouldn't have been installed hence needing to do it now.
@seb, your clean install process would have included the dev pack behind the scenes (at least that is what I'm gathering from looking into the information). This is why you get two different lots of behaviour and it works nicely on the clean install :-)
I installed on a clean Win 10 1809 VM, nothing installed before, did NOT opt to install the 4.7.2 dev pack and things still worked for me.
On a clone of that machine I did install the dev pack and then removed it again, which still worked. So I'm almost 100% sure the dev pack is not needed.
Hmm, interesting, I've had to install the dev pack on 4 different machines :-) Just installing the runtime wouldn't get it to show up in VS (these weren't clean builds).
v8 preview via nuget.... doesn't seem to fetch umbraco dlls, or reference them in the solution?
https://github.com/umbraco/UmbracoDocs/edit/master/Getting-Started/Setup/Install/install-umbraco-with-nuget.md
following the instructions, with one change..
when building (Ctrl+f5 from vs 2017) the successfully installed nuget package.. I get
It looks like all the required umbraco dlls aren't being propagated into the bin folder (they don't appear n the solution references either), are there dependencies missing in the nuget package?
I do have a v8 up and running via cloning the whole source from github.. but just wanted a release binary to play with and though nuget would be it?
That works on our machines, maybe try again?
Requirements are: .net 4.7.2 and the latest updates for VS17 should be installed.
That could be it.. the default for a empty asp.net web application seems to have set to 4.6.1 for me, though 4.7.2 is available.
I presume you mean visual studio 2017 community (or other flavour).. (I've version 15.9.5)
Should it work in visual studio code too?
Away at the moment, but will try later and let you know. Thanks!
All editions are basically the same. 15.9.5 is perfect.
You can't install NuGet packages in VSCode, so no :-)
Setting the framework target for the empty asp.net web project to v4.7.2 was the missing link.
As per the cloned source requirements, do we also need the 4.7.2 developer pack (I'd installed that as well already so not sure if needed or not)?
Not sure, but doubt it. it should just run on the .net framework itself, dev pack would be for developing Umbraco from source.
Hi,
Had the same issue. Had to install .NET Framework 4.7.2 Developer Pack.
Can UmbracoHQ add a verification on nuget package to validate the .NET framework on the current project?
Thanks, Pedro
Not sure what more we can do @Pedro, we already require .NET 4.7.2 : Maybe we can make it more strict? If you know how to, I would love to hear about it:
Maybe add a note in the readmeUpdate.txt file, next to the "Don't forget to build!"
Don't forget to build, and double check that your project is a .Net Framework 4.7.2!
:)
Aha, here's a simple thing we can do, if we force NuGet to have to be at least version 4.6.0 then people will need to update to a pretty recent VS version first, that should help a lot.
I have the latest version of VS but not the latest version of .net :(
Just to check: which Windows version are you using?
Thanks, but you can already only install it if Framework 4.7.2 is installed, the Developer pack is not necessary, I don't have it installed... 🤔
I'll need to test it on a VM to be sure.
Just to confirm, on a clean VM (Win 10 1809) with VS2017 15.9.7 and no 4.7.2 developer pack installed, Umbraco 8 does install correctly. It's going to be difficult to figure out what exactly was wrong on your machine but I guess a side-effect of installing the developer pack is that "something" got fixed.
Thank you @Sebastiaan.
If you need more specs from my machine let me know.
H5YR U8, Pedro
As an FYI on this... depending on the state of your machine and when things were installed you "may or may not" have had the "dev pack" installed when VS installed.
If your machine had VS2007 on before you upgraded Win 10 to the creators edition then the Dev Pack for 4.7.2 wouldn't have been installed hence needing to do it now.
@seb, your clean install process would have included the dev pack behind the scenes (at least that is what I'm gathering from looking into the information). This is why you get two different lots of behaviour and it works nicely on the clean install :-)
I installed on a clean Win 10 1809 VM, nothing installed before, did NOT opt to install the 4.7.2 dev pack and things still worked for me.
On a clone of that machine I did install the dev pack and then removed it again, which still worked. So I'm almost 100% sure the dev pack is not needed.
Can't hurt though, I'm sure.
Hmm, interesting, I've had to install the dev pack on 4 different machines :-) Just installing the runtime wouldn't get it to show up in VS (these weren't clean builds).
is working on a reply...