Error only in automated MSBuild

[Miyuru]

When my Telerik test project build in build server I get the following error:

C:\Program Files (x86)\MSBuild\Telerik\WebUITestStudio\Telerik.WebUITestStudio.targets(9,5): error : Unable to determine the project namespace. Please make sure the settings file is available.

I have installed Telerik Test Studio on this server. Attached the solution.

[Cody]

Hi Miyuru,

That error message means that Test Studio was unable to locate the "settings.aiis" file when it was time to regenerate the "Pages.g.cs" file as part of the build. To figure out what is causing this problem we have to have look at your build server and build configuration.

1. What are you using for your build server?
2. If using Visual Studio or TFS, which version? 2010? 2012?
3. Does the build process automatically get latest from source control?
4. Is the setting.aiis file checked-in to source control?
5. What is your build definition?

Regards,
Cody
Telerik

[Miyuru]

1. What are you using for your build server? Microsoft Windows Server 2003 R2
2. If using Visual Studio or TFS, which version? 2010? 2012? TFS 2010
3. Does the build process automatically get latest from source control? Yes
4. Is the setting.aiis file checked-in to source control? Yes
5. What is your build definition? DefaultTemplate.xaml that comes with TFS

[Cody]

Hi Miyuru,

I happen to have a test TFS 2010 server setup. Using your project I was able to reproduce the problem. I filed a bug on this here.

Fortunately there's an easy work around. Add this command to the Pre-build event command line.
copy "$(ProjectDir)settings.aiis" "$(SolutionDir)"

The build will now succeed. Thanks for reporting this issue. I suspect (but not 100% sure) it's a regression. I believe this used to work months ago.

Regards,
Cody
Telerik

[Miyuru]

Hi Cody,

Thank you for the reply. I tried the workaround that you have suggested and I still get the same error. I have attached build log file for your reference.

Thanks,
Miyuru.

[Cody]

Hello Miyuru,

That just doesn't make sense to me. For comparison purposes I've attached the log from my build or the same PoC project. I am using our latest internal build, 2012.2.1527. I'd like you to try upgrading to this version to insure we're using the same build of Test Studio. You can download it from Telerik.com after logging in, then going to Latest Internal Builds.

Regards,
Cody
Telerik

[Miyuru]

Hi Cody,

I download the latest Internal Build version and installed it on my build server. Still I get the same error :-(

Thanks,
Miyuru.

[Cody]

Hello,

I'd like to look at this problem on your computer via GoToMeeting. Let me know what time zone you are in and your availability and I'll setup the meeting. I'm in Austin, TX which is Central Time (GMT -6).

Regards,
Cody
Telerik

[Cody]

Hello Miyuru,

Here is a meeting invite for later today:

1.  Please join my meeting, Monday, July 08, 2013 at 1:30 PM Central Daylight Time.
https://global.gotomeeting.com/join/160530469

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.

Dial [phone]
Access Code: 160-530-469
Audio PIN: Shown after joining the meeting

Meeting ID: 160-530-469

Regards,
Cody
Telerik

[Cody]

Hi Miyuru,

Here's a summary of our meeting today:

• The main symptom is "Unable to determine the project namespace. Please make sure the settings file is available."
• I discovered that Visual Studio is installed on the D: drive. I am suspicious there's a bug in Test Studio with this setup.
• You will try getting VS installed on the C: drive instead.
• We will try to reproduce this by setting up a build machine with Visual Studio installed on D: drive.

Regards,
Cody
Telerik

[Plamen]

Hi Miyuru,

It turned out the problem is that you are referencing the Telerik DLLs from the "ExternalAssemblies" folder. Please try referencing the DLLs either from the GAC or from the Test Studio's Bin folder. See this video for more information.

Another option is to try our new R1 Beta release where this issue should be fixed. Here is a direct link to the new R1 BETA installer through your Telerik account.

Regards,
Plamen
Telerik