Telerik Testing Framework only uses ASP.Net 2.0 Web Development Server?

7 posts, 0 answers
  1. Erich
    Erich avatar
    3 posts
    Member since:
    Nov 2012

    Posted 14 Nov 2013 Link to this post

    I'm using Telerik Testing Framework (version: 2013.1.911.0) and I'm trying to use the Run Local Web Server feature. The MVC app I'm testing is using 4.0 so I set the localWebServer setting to "AspNetDevelopmentServer40". When I run my tests though I get an error in the browser:

    Unrecognized attribute 'targetFramework'.

    Then I look in my system tray and the development server is running version 2.0.50727.5459. This explains the error but localWebServer setting should be set correctly. I'm using Visual Studio 2012 to develop the application and tests (which are using the VSUnit template with all of the settings in an App.config).

    Help would be greatly appreciated.
  2. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 19 Nov 2013 Link to this post

    Hi Erich,

    I apologize for the delay getting back to you. I assume you're following this documentation? I need to double check with our software developers, but I am pretty sure the ASP.NET 2.0 server is all we support at this time. We probably should update this and add a new browser type such as "AspNetHost40" to go along with our existing AspNetHost browser type.


    Regards,
    Cody
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  3. Erich
    Erich avatar
    3 posts
    Member since:
    Nov 2012

    Posted 19 Nov 2013 Link to this post

    Thank you for the reply!

    Actually I was following one of the samples that is part of the Telerik Testing Framework samples (AspNetAndTestRegions.cs). The example does use the legacy development server but the LocalWebServerType enum has three values:

    AspNetDevelopmentServer
    AspNetDevelopmentServer40
    None

    I assumed AspNetDevelopmentServer40 was the new development server, is it not implemented?
  4. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 26 Nov 2013 Link to this post

    Hi Erich,

    I apologize for the delay getting back to you. I have confirmed this appears to be a bug in our framework. As a temporary work around you can go to the folder where the development web server files are stored and rename all WebDev.WebServer40 files (there should be 3 of them) to WebDev.WebServer20. Of course you'll want to save a copy of the original WebDev.WebServer20 files first. This will force our framework to launch the 4.0 server instead of the 2.0 server. On my machine the files were located at:

    C:\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0

    Regards,
    Cody
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  5. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 26 Nov 2013 Link to this post

    Hello,

    I am sorry, I included the wrong link to the bug report. Here's the correct link:
    http://feedback.telerik.com/Project/117/Feedback/Details/66343-setting-localwebserver-to-aspnetdevelopmentserver40-will-launch-the-2-0-server-in


    Regards,
    Cody
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  6. Erich
    Erich avatar
    3 posts
    Member since:
    Nov 2012

    Posted 27 Nov 2013 Link to this post

    Thank you for the response and work-around! I've tried your work-around and it works (fortunately I don't have any legacy apps to worry about)!
  7. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 27 Nov 2013 Link to this post

    Hello Erich,

    I am glad to hear it, thank you for the update. Hopefully it doesn't take too long for us to fix this bug.

    Regards,
    Cody
    Telerik
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
Back to Top