While debugging VS complains "Changes were made to Pages.g.vb"

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 01 Oct 2013 13:10 by ADMIN

ADMIN

Cody

Created on: 21 Mar 2013 14:47

Type: Bug Report

While debugging VS complains "Changes were made to Pages.g.vb"

When you attempt to debug a coded step using VB code using our VS plug-in, VS complains:

Error	1	Unable to apply this change while debugging. File 'C:\GSI_Projects\SQA\Automation\Main\Source\MultiProjectSolution\Scripts\Pages.g.vb' was reloaded. You must revert the change or stop the debugging session.	C:\GSI_Projects\SQA\Automation\Main\Source\MultiProjectSolution\Scripts\Pages.g.vb	1	1	Scripts

You are now completely blocked from continuing execution.

4 comments

ADMIN

Iliyan Panchev

Posted on: 01 Oct 2013 13:09

The problem occurs when the pages.g.vb file is open in Visual Studio. If you close the file, this issue should be gone.

ADMIN

Konstantin Petkov

Posted on: 28 Mar 2013 11:03

Yes, I do understand how this hamper all the process, it's quite annoying.

I got an update from the QAs. They were able to replicate the problem on a specific machine with an earlier build but installing the latest internal build (we published it yesterday) they cannot replicate it anymore on the exact same machine. And this is both VS 2010 and VS 2012 so it shouldn't matter the VS version. 

I wonder if reinstalling on your end can help. Can you try our latest internal build (labeled 2012.2.1527) and let us know if that helps? Thanks!

Patrick

Posted on: 27 Mar 2013 16:02

We are currently using varied versions of VS 2010.  Do you think VS 2012 would make any difference (without harming what we currently have) ?

When creating a script we delete any reference to Pages in our initial file, would a copy of one of our tstest.vb files help find a solution?

Unfortunately for us, this issue makes debugging a full "stop & restart" everytime problem, making the script creation process much longer than initial expected on top of the future runtime issues we already expected due to its compiled nature.

ADMIN

Konstantin Petkov

Posted on: 22 Mar 2013 14:39

We had this issue reported a while ago and tried to investigate it. Unfortunately both the developer and QA department were unable to get a solid repro and I believe it's just out of our control and is VB compiler specific issue in VS. I asked the QA dept. to check that today in VS 2012 and they report they cannot replicate it there. I'm sorry we cannot do much in this case.