I installed Visual Studio 2013 RC on Windows 7. I want to work with Browser Link Dashboard. But It isn't working. It shows that No Browsers Connected in the Refresh link. What should I do? Please Help
to me what worked
<system.webServer>
<handlers>
<add name="Browser Link for HTML" path="*.html" verb="*"
type="System.Web.StaticFileHandler, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
resourceType="File" preCondition="integratedMode" />
</handlers>
</system.webServer>
You need to be debugging a project that includes the right HttpModule for Browser link to work.
It is mentioned in this post.
An MVC project and Web forms will include the HttpModule that inserts the required JavaScript code into your pages for Browser link to work.
You can check that the bottom of your page have the following (view source):
<!-- Visual Studio Browser Link -->
<script type="text/javascript" src="/__vwd/js/artery"></script>
<!-- End Browser Link -->
An empty ASP.NET project does not work out of the box.
Copying the following from an MVC project into the web.config of an empty ASP.NET project will insert the magic JavaScript, but it will also stop your page from displaying. Not sure how to just get the HttpModule that is needed and not the MVC view blocking. Visual studio will report that the browser is connected though.
<system.webServer>
<handlers>
<remove name="BlockViewHandler"/>
<add name="BlockViewHandler" path="*" verb="*" preCondition="integratedMode" type="System.Web.HttpNotFoundHandler" />
</handlers>
</system.webServer>
Related
I've created a WebSite Project in Visual Studio 2019, but when I try to add an ADO Entity Model and I click on New COnnection, Visual Studio raise an error:
assemblyFile is null or empty
at Microsoft.Data.Entity.Design.VisualStudio.ExecutorWrapper...
After clicking on Abort, the only button that can close the error window, VS crashes.
I've tried to reinstall everything from scratch several times, I've installed also on another PC but the error persists.
The reference to the assembly System.Data.Entity is in the webconfig:
<compilation debug="true" targetFramework="4.7.2">
<assemblies>
<add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data.Entity.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
</assemblies>
</compilation>
Anyone knows how to solve or Database first in EF6 must be forget??
This happen to me on a website project. I change it to use Web Application project and now EF works fine. Try that.
I just adquired the VS 2012 and I tryed to open my projects I made using VS 2010.
But now, the ReportViewer is not working, it shows up but with NO DATA.
my code are OK, my querys are OK, everything about this are OK, I'm sure !!
Because it's not working only now in the Visual Studio 2012, anyone would know what could I do ?
I tried to remove some lines from my web.config:
<add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
<add assembly="Microsoft.ReportViewer.Common, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
I also tried to delete my current ReportViewer and Create a new one, didn't work neither...
Obs: I'm not posting any code here because I have no need to correct my code, it's ok, I'm sure ! I just need know why it's not working on VS 2012.
Make sure you have updated your aspx page hosting the reportviewer with the reference to the version 11.
<%# Register Assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>
I am having a version problem with the ReportViewer Control. I am using visual studio 2010, but I think I need to use the 2005 report viewer because I am using SQL 2005. So, I set the webconfig file to point to the 2005 ReportViewer .dlls, everything works once, then VS edits the web.config to point to the 2010 versions of the dlls. Here is the relevant web config file sections set what I think is correctly:
<httpHandlers>
<add path="elmah.axd" verb="POST,GET,HEAD" type="Elmah.ErrorLogPageFactory, Elmah" />
<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
validate="false" />
</httpHandlers>
<compilation>
<assemblies>
<add assembly="Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
</assemblies>
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>
</compilation>
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
<handlers>
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd"
type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</handlers>
So, after running it and it working a few times, it automatically changes the version of the http handler to 10.0.0.0. How can I prevent this?
What is written to the web.config is defined by the references you use in the project.
In my Visual Studio 2008 project, I have the following references:
Microsoft.ReportViewer.Common.dll (Version 9.0.0.0)
Microsoft.ReportViewer.WebForms.dll (Version 9.0.0.0)
So in my config I see:
<system.web>
...
<compilation>
...
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>
</compilation>
...
<httpHandlers>
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
</httpHandlers>
When I look at the available project references I have three:
Version 8.0.0.0
Version 9.0.0.0
Version 10.0.0.0
I assume this is because I have Visual Studio 2005, 2008, and 2010 installed, but perhaps installing the individual report viewer redistributables would offer the same selection:
MS Report Viewer 2005 (Version 8.0.0.0)
MS Report Viewer 2005 SP1 (Upgrade) (Version 8.0.50727.42)
MS Report Viewer 2005 SP1 (Full Install) (Version 8.0.50727.42)
MS Report Viewer 2008 (Version 9.0.0.0)
MS Report Viewer 2008 SP1 (Version 9.0.0.0)
MS Report Viewer 2010 (Version 10.0.0.0)
N.B. I've made best guesses at the version numbers; if you know better please correct me.
It is not an exact answer to your question but probably the solution.
There is no need to use older version of report viewer. It is independent on the server. Especially with .rdlc (client reports) you provide only data and report does not know the server.
It is possible to access SQL reports with a win forms app. developed using VS2010 with the ReportViewer Component Version=9.0.0.0.
Here are the steps:
To access SQL 2005 reports, you are going to have to use Version=9.0.0.0 of the report viewer component, as stated above. So you will need this in the .aspx page which you want to render the report or in a master page which it inherits:
Register assembly="Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" namespace="Microsoft.Reporting.WebForms" tagprefix="rsweb"
And this
<form id="foo" runat="server">
<div>
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<rsweb:ReportViewer ID="ReportViewer1" runat="server" ProcessingMode="Remote" Width="950px"
Height="600" BorderColor="Gainsboro" BorderStyle="Solid" BorderWidth="1px">
<ServerReport ReportPath="/foo/foo/FooReport"
ReportServerUrl="http://foo/ReportServerSQL2005" />
</rsweb:ReportViewer>
…
You might have to change references to any other version of the ReportViewer Component in the web.conig as well because VS2010 and newer versions are going to default to new versions of the ReportViewer Component
e.g.
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
Change to
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
Just search the entire solution for Version=8.0.0.0 and Version=10.0.0.0 etc. and make changes to both the Version= and PublicKeyToken=
You are also going to need a reference in your project to the reportviewer component 9.0.0.0, from the .net tab and remove any references to any other version.
It’s worth noting that when using .aspx pages which have both source and design views in VS, it will say Error Creating Contol – ReportViewer1, in the Design view. From what I have read, this is a bug with the component but it works anyway in all major browsers.
Also, if you are going to drag the component from the tools onto the design surface, you are most probably going to need to add the 9.0.0.0 version and ensure that it is this one that you use.
I previously answered this question here:
http://forums.asp.net/p/1985629/5691326.aspx?VS2010+ReportViewer+with+SQL+2005
However, my application is .NET 3.5 MVC2 application but I was still able to get it to render SQL2005 reports, after some considerable effort.
Ideally you should update your 2005 SQL report services to 2008, however, make sure that everything still works by creating a copy/backing up first because there is no going back. Once you have achieved this, all of the above becomes unnecessary, for us this was just an interim solution.
When I open a solution containing an MVC3 project in Visual Studio 11 Beta, I see the following message:
The Web project 'Landboss.Web' requires missing web components to run
with Visual Studio. Would you like to download and install them using
the Web Platform Installer now? (Note: Some components might require
restart to take effect.)
ASP.NET Web pages with Razor syntax 1.0.0.0
When I click Yes, the Web Platform Installer opens and tells me this:
The product you are trying to install is not supported on your
operating system. Click here for more information.
So far I've installed Visual Studio 11 Beta on two machines and both have this same problem.
I believe this was caused by the fact that I had previously installed Visual Studio 11 Developer Preview. I did uninstall it before installing the Beta, but you know how that goes.
To fix it, I did the following:
Uninstalled "Microsoft ASP.NET MVC 3 - Visual Studio 11 Tools Update"
Uninstalled "Microsoft ASP.NET Web Pages - Visual Studio 11 Tools"
Ran the Visual Studio 11 Beta "Repair" from the installation ISO.
It worked! Razor syntax highlighting and intellisense are back, and the warning message no longer shows when I open the project.
This is related to the configuration setting webpages:Version
[appSettings]
...
[add key="webpages:Version" value="x.0.0.0" /]
...
[/appSettings]
if you have multiple versions of razor on the system (1 or 2 for now), better add this setting if it's missing.
Choose the version you want/need at the appropriate level. (Obviously replace the brackets...)
I have also had this error happen when a Subversion conflict was committed to the repository - the presence of this block in the web.config's app settings seemed to trigger the message when loading the project:
<<<<<<< .mine
<add key="blogCommentsApprovedByDefault" value="false" />
(other appsettings)
=======
<add key="blogCommentsApprovedByDefault" value="false" />
(other appsettings)
>>>>>>> .r358
Cleaning up the Subversion conflict in appSettings resolved this error.
While #silent__thought's solution may correct the problem, it's not the easiest way to fix it.
#Costas solution may exactly address the problem, but here is a more detailed explanation if you need it.
In my case, I needed the following in my web.config file (for MVC 4):
<configuration>
<appSettings>
<add key="webpages:Version" value="2.0.0.0" />
<add key="webpages:Enabled" value="false" />
<add key="PreserveLoginUrl" value="true" />
<add key="ClientValidationEnabled" value="true" />
<add key="UnobtrusiveJavaScriptEnabled" value="true" />
</appSettings>
<system.web>
<compilation debug="true" targetFramework="4.0" />
<pages>
<namespaces>
<add namespace="System.Web.Helpers" />
<add namespace="System.Web.Mvc" />
<add namespace="System.Web.Mvc.Ajax" />
<add namespace="System.Web.Mvc.Html" />
<add namespace="System.Web.Routing" />
<add namespace="System.Web.WebPages" />
</namespaces>
</pages>
<httpHandlers></httpHandlers>
</system.web>
</configuration>
Of course, you may not need all of these configurations for your app. These just happen to be the default settings for an MVC 4 project.
I got this error because the appSettings section was setup to be encruypted, and the encryption keys were not setup correctly. It seems this error has a tendancy to popup whenever there is something wrong/malformed with web.config even if unrelated to MVC.
I got this error when something in the web.config file was corrupted. I simply formatted the file and then resaved it. Then I restarted Visual Studio.
I've just been bitten by this and it's another variation of the web.config problem. In my case we do not store a web.config file in our repo but generate one from a template as a custom build step. When we do a clean of the workspace* this file was being deleted (rightly so because it's not in the repo) and so the next time Visual Studio was started it complained. A command line build via msbuild was never affected by this.
*We have a "partial" clean, which deletes all the build artefacts (including those VS leaves behind) and a "full" clean that resets the workspace to the same state as if you had just pulled it from the repo.
I've created a new Application that points to the files. It is running in ASP.NET 4.0 Integrated App Pool.
The files are just a couple of CSHTML files and some CSS/Javascript.
When the files were HTML I was able to hit them just fine. Now that they are cshtml, I get
This type of page is not served
when I try to hit the Directory/File.cshtml in a browser.
I usually write MVC3 apps, but this is just a simple 2 page site that needs to be up. I'm not familiar with deployment of these types of projects. Any advice would be helpful.
My web.config is simple and looks as follows:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<compilation debug="true" targetFramework="4.0" />
</system.web>
<system.webServer>
<defaultDocument enabled="true">
<files>
<add value="MyFile.cshtml"/>
</files>
</defaultDocument>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
</configuration>
Thanks in advance for your help!
To fix this, install the "ASP.NET MVC 3 (Visual Studio 2010)" package using the "Web Platform Installer" (http://www.microsoft.com/web/downloads/platform.aspx).