VS compilation debug but not release

Question

1.00/5 (2 votes)

See more:

I Like to compile only in debug. Right now I have compiled in Debug but not in Release and when pressing F11 on a certain line I get this message:

The source code file is different since the module was generated. Do you want the debugger to use it anyway?

What I have tried:

in all the sites of internet.

in all the sites of internet.

Posted 12-Sep-19 2:42am

zequion

Updated 12-Sep-19 2:52am

v2

Add a Solution

2 solutions

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)

CHill60 · Answer 1 · 2019-09-12T02:50:00

Solution 1

The message is quite clear - your debug information is out of step with your code.
Clean your solution and do a full rebuild and the problem should go away

Posted 12-Sep-19 2:50am

CHill60

OriginalGriff · Answer 2 · 2019-09-12T02:53:00

Solution 2

F11 is "Step into" in Visual studio debugger - so if you get different results with the release and debug version then the chances are that you have different binaries for an assembly you are stepping into in the bin/debug and bin/release folder (or at least, different modification / creation dates)
Check them all manually, and see what you can find out.

Posted 12-Sep-19 2:53am

OriginalGriff

Comments

[no name] 12-Sep-19 8:56am

The problem is that I don't want to compile all the time in Debug and Release. I just want to compile in Debug, but when pressing F11, when the line changes the .cs file, that error appears.

F-ES Sitecore 12-Sep-19 9:07am

You don't have to compile in release, just debug, and if you change the code then you have to stop debugging and re-compile

[no name] 12-Sep-19 9:40am

I have the .cs in a dll called common.dll
The message says that the dll in \bin\debug\common.dll has changed since the code was generated (compiled only in debug)

OriginalGriff 12-Sep-19 9:58am

Yes - check the file timestamps.
If they are later than the EXE (or DLL you are targeting) then the system want's to know why...

[no name] 13-Sep-19 7:39am

I have verified that:
If I compile the dll in debug, the dll time in \ bin \ debug is updated well. If I compile Release the dll time is updated well in \ bin \ release

If I modify and compile in debug, but not in Release, I get the error message indicated. But now I have seen that if I compile in Release, but not in debug, I can execute and stop the execution as if it were Debug and continue with F11 and the error does not appear.

It seems that something has been changed internally that makes it recognize Release as Debug and vice versa.
Any solution?

OriginalGriff 13-Sep-19 8:41am

Without being able to see you machine, it's guesswork from this end, but ... I'd suspect that your builds are working to the same DLL file, rather than the Release and Debug version of that file. I'd check the project References and see where you set it to - and include the project if possible instead of just the DLL file.