Compile failed on remote execution

[Uroš]

Suddenly I have encountered a compile failed error on remote execution. I got the following error under results:

 

Compile failed: c:\Users\Administrator\AppData\Local\Temp\2\Projects\172eb586-88ca-49d8-ba54-77c7a827f982\Trunk\Pages.g.cs(8826,39) : error CS1519: Invalid token '' in class, struct, or interface member declaration

 

Local execution is working OK. What could be the reason for such behaviour?

 

 

[Elena]

Hello Uroš,

Thank you for contacting us. 

In order to advice you best, please share further details on the issue you experience. 

- Were you able to execute your project remotely successfully before?
- Is there anything you changed in your setup to encounter this error? 
- Are you using a source control system (TFS)?
- Do you have a Test-as-Step inserted in a coded step in your project? 

Please try to reproduce this error and provide us the application log file. Here is a short article how to enable the log and collect it. Please clear the log before reproducing the error. 

It would be great if you could provide us your project as well, or, if not possible, a sample reproducing the same error. 

Thanks in advance for the cooperation. 

Regards,
Elena Tsvetkova
Telerik

 

[Chun]

I have experienced similar situations a handful of times. Some suggestions...

• Open your project in Visual Studio, Clean your solution, Build your solution. This seems to help a bit when this happens.
• Test Studio's latest internal build gives users the ability to compile from the Test Studio IDE. I was thinking about upgrading to it for the same exact issue you are experiencing but would prefer to wait for a stable release.
• Make sure you have dirtied your tests you are attempting to run remotely. An observation I have made. If you make changes to .tstest.cs files in Visual Studio and do not open the corresponding .tstest file in Test Studio & view it (at which point the test is displayed in the project explorer in bold) after doing so...Test Studio will not pick up the change(s) you made to the given coded step(s).

Good luck. This error is rather unfortunate because you don't have control as to how the Pages.g.cs file is created. In other words, you should never have to edit or fix it.

Let us know how it goes.

[Elena]

Hello guys,

@ Uroš: Let me know if you managed to figure out a solution for your scenario or you will need additional assistance. Please if so, share some details on what you tried and what the result was.

Thank you in advance for the cooperation. 

@ Chun: Thank you for sharing your experience. I appreciate it a lot. 

Regards,
Elena Tsvetkova
Telerik