+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Are there any known issues with Sitefinity version: 6.1.4300.0 and Visual Studio 2013?

Are there any known issues with Sitefinity version: 6.1.4300.0 and Visual Studio 2013?

6 posts, 0 answered
  1. Grey
    Grey avatar
    9 posts
    Registered:
    09 Sep 2013
    25 Nov 2013
    Link to this post
    Are there any known issues with Sitefinity version: 6.1.4300.0 and Visual Studio 2013? I'm the first on my development team  to make the move from VS 2012 to VS 2013 - but (for instance) I can't run sitefinity in Chrome (get this error):
    ***************************************Server Error in '/' Application.Post cache substitution is not compatible with modules in the IIS integrated pipeline that modify the response buffers.  Either a native module in the pipeline has modified an HTTP_DATA_CHUNK structure associated with a managed post cache substitution callback, or a managed filter has modified the response.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Post cache substitution is not compatible with modules in the IIS integrated pipeline that modify the response buffers.  Either a native module in the pipeline has modified an HTTP_DATA_CHUNK structure associated with a managed post cache substitution callback, or a managed filter has modified the response.
    ***I tried applying the solution posted here:http://www.sitefinity.com/developer-network/forums/general-discussions-/post-cache-substitution-is-not-compatible-with-modules-in-the-iis-integrated-pipeline-that-modify-the-response-buffersbut to no avail...
     
    ***************************************
    and in Internet Explorer I get errors js errors every time I change screens:***************************************JavaScript critical error at line 580, column 15 in http://localhost:1604/85e06971e21d4a788ea0873eda68efdf/browserLink\n\nSCRIPT1010: Expected identifierJavaScript critical error at line 580, column 15 in http://localhost:1604/85e06971e21d4a788ea0873eda68efdf/browserLink\n\nSCRIPT1010: Expected identifier***************************************Any help is greatly appreciated,G
  2. Vassil Vassilev
     Vassil Vassilev avatar
    308 posts
    Registered:
    21 Jan 2015
    28 Nov 2013
    Link to this post
    Hello Grey,

    Visual Studio 2013 is not supported officially thus in specific cases there could be some unexpected results. For the moment this are system requirements officially announced and supported (IDEs - Visual Studio 2010&2012) 

    Regards,
    Vassil Vassilev
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Christopher
    Christopher avatar
    3 posts
    Registered:
    24 Jun 2008
    18 May 2014 in reply to Grey
    Link to this post
    I'm not sure if you are still having this error, or if this is the root of the problem.  I saw the same thing in VS 2013 and wound up turning off the browser link feature that is unique to VS 2013.  Once I did that, the error stopped occurring.
  4. Stacey
    Stacey avatar
    291 posts
    Registered:
    18 Oct 2012
    19 May 2014 in reply to Christopher
    Link to this post

    I was getting the same error with CacheSubstitution and disabling BrowserLink took care of it for me too.

  5. Chris Ray
    Chris Ray avatar
    4 posts
    Registered:
    20 Apr 2012
    12 Jun 2014
    Link to this post

    Worked for me too. Thanks. 

    http://www.poconosystems.com/software-development/how-to-disable-browser-link-in-visual-studio-2013/

  6. Bain
    Bain avatar
    2 posts
    Registered:
    19 Nov 2014
    01 Jun 2015
    Link to this post

    Hi Guys,

    The disabling of BrowserLink worked for me too

6 posts, 0 answered