Adding a page in 4.1 using VS 2017. Microsoft.VisualStudio.Web.Codegeneration.Design 2.1.2 not an available Nuget package

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
5 years ago
Greetings from wintry Austin Texas,

ref:
nopc 4.1 source pulled newly this morning 1-13-19
Solution opened in using Visual Studio 2017 Ent
initial clean, package restoration,  build ->
run -> db install -> run,  site loads, all good
add a view in nop.web
scafolding starts, errors out with the 2.1.2 dependency break and ..no view.

There is a dependence in Nop.Web on Microsoft.VisualStudio.Web.Codegeneration.Design 2.1.2
however, Microsoft.VisualStudio.Web.Codegeneration.Design 2.1.2 is NOT an available nuget Package.
Choices: 2.1.1 or 2.1.3
Rebuild gets 2.1.3 however adding a new view doesn't complete and nop.web Dependencies shows with a yellow/black ! icon indicating the breakage because 2.1.2 is expected and adding a view breaks with 2.1.3.

Anyone run into this?

My reason for adding a view is
I'm on 4.1 using VS 2017 ENT, and looking in the dev documentation for the "how to" on adding a new page in 4.1.
I didn't find anything.  I want the BLOG page open on the index.cshtml, showing posts, front and center.

This used to be pretty straight forward!   anyone know how to add a page in 4.1 and or clear the dependency break?  


Best,
Rich
5 years ago
There's no reason adding a .cshtml View would cause any issue. You just add a .cshtml file, and refresh browser, and the problem appears?


5 years ago
Yes.
Adding the new page doesn't complete.
After naming the page, click ok, the process begins and errors out during scafolding.

Have you sandboxed pulling 4.1 source,  running through the install, adding a page,etc.
No problem?

Rich
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.