The type or namespace name 'LoginViewModel' could not be found

Question

1.00/5 (2 votes)

See more:

Building small brochure-ware MVC website with no authentication. It's disabled in Visual Studio. Published with Visual Studio 2015 to my workstation IIS successfully the first time. Now when I attempt to publish again I get "The type or namespace name 'LoginViewModel' could not be found..." and a bunch of additional errors seemingly connected to login authentication.

How do I get around this?

Posted 6-Nov-15 11:43am

mlowry

Add a Solution

Comments

PIEBALDconsult 6-Nov-15 18:48pm

Huh. That sucks.

Krunal Rohit 6-Nov-15 23:21pm

Whenever you publish, always rebuild the project.

-KR

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

mlowry · Accepted Answer · 2015-11-07T02:58:00

After some digging I discovered that Visual Studio had inserted a series of "Account" views even though I specified no authentication when I initiated the project. These would build OK in test mode, but would fail when publishing to my test server. Removing the Account views fixed the problem.