I have been using an old versión (April 2010) succesfully and I decided to upgrade to the latest versión (Dec 2013). All .NET.35 (Same as my project)
I have a page that is using a few extenders (Confirm and Autocomplete) that was working fine, the moment that I upgraded the library the page upon displaying keeps reloading in a loop.
I have removed all references to the Control Toolkit and and then it does not do it anymore, but the moment I just introduce the:
The cc1 is defined in the web.config under Pages/Controls as:
With the new library it starts an endless reloading again.
If I put back the .NET35 from April 2010, all works again
Any ideas/suggestions that any of you has heard about this issue?
Thanks
Pete
Related
I have installed Resharper's Trial version followed by OzCode extension and at some point of time, navigating to Definition capability in aspx web forms got broken. It is killing my productivity and I would really appreciate some suggestions.
What I have tried -
Following every suggestion in this SO POST
Deleting Resharper's Extension using this Post
None seems to be helping. Attaching the image too.
Edit - 1
I am also not able to navigate to javascript functions :(
We have an Asp.Net 4.5 WebForms application that we still maintain. It uses WebForms with master pages. In VS 2019 the Go to Defintion option is completely missing when I select a form's button event and right-click. The same result when pressing the F12 key which should take me to the method definition for GetTokenButton_OnClick in the code behind page, nothing happens.
This all still works nicely in VS 2017.
Have MS dropped full support for Webforms in 2019 or am I missing an add-on or something?
This is right-click on the button event in 2017:
This is 2019> Notice how many functions are missing:
UPDATE:
I have the same issue with a class library that is part of the same solution. When hitting F12 on any of the class library's objects referred to in the web project's code, I get the dreaded "cannot navigate to symbol under the caret" error. What is strange is that everything builds and executes.
I had this issue earlier today after updating to VS2019 and tried all the solutions I found in Go To Definition: "Cannot navigate to the symbol under the caret.". None of those worked, but I solved it by updating the Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers versions in my NuGet Packages for the solution.
Right-Click the solution file and click 'Manage NuGet packages for this Solution'
Under Updates, search for 'compiler'
I updated both Microsoft.CodeDom.Providers.DotNetCompilerPlatform and Microsoft.Net.Compilers to versions that other solutions we maintain use. These were 1.0.8 and 2.4.0 respectively in my case.
After that, definitions and symbols started working again.
Believe it or not but I am still maintaining this WebForms app and this now seems to have been resolved. I'm now running Visual Studio Entrerprise 2019 version 16.9.4 and the go-to-definition option is back.
I'm trying to get a VB ASP.NET website (for which I was given the code) running in VS 2010. It uses telerik controls. I downloaded and installed the latest version of Telerik ("RadControls for ASP.NET AJAX v. 2016.1.225.0")
When I open the project in VS 2010, though, and open the Toolbox, it shows as Telerik control categories, "Telerik AJAX Controls [Bla] 2012 Q1 NET 35"
I would expect to see "... 2016.1.225.0" or "... 2016 Q1 NET 35" instead.
I don't know if having the older version of the controls is the problem or not (the developer who sent me the code is using an old version, too).
But I'm getting tons of compiler messages (the first one of the 123 showing, in fact, is "Maximum number of errors has been exceeded"), and I wonder if this version mismatch is the, or one of the, culprits. After that, there are several "Type 'SQLServer' is not defined" errors (among others) appear.
So should I upgrade my project to use the latest Telerik download, and if so, how can I accomplish that?
Delete and re-add the reference to the new version. Every time you upgrade, there can be an issue of compatibility issues; I've been a long time user of Telerik and we occassionally get errors after upgrading. Since youre version is about 4 years different, the best way is probably to just add the new reference and fix all of the compile and runtime errors...
I assume that the real reason for the errors you are getting is possibly other supporting DLL's not being installed on your machine (GAC references) that are on that developer's machine. For instance, SQLServer errors would probably be referring to one of the Microsoft SQL Server type libraries... It doesn't hurt to upgrade to the latest if you have the time, but that might not solve all the problems you are experiencing.
In the visual studio menu bar we have telerik menue in that go to "upgrade" . in the wizard it will show the latest telerik reporting dll you have and will update it .
My hard drive died recently so I had to install visual studio 2010 all over again. With this version of VS anytime I click on a control (like text box or gridview) the properties section doesn't update. Even when i right click on the control and click view properties it doesn't update ... The only way i can get the properties tab to update is by building the project (but i have to do this every time i want to view properties of a control). I have uninstalled and reinstalled (VS 2010 and SP1) but neither have had an effect on the issue.
I have also tried turning off the add-ons as i thought this might affect performance (but not joy). I also have Visual Studio 2008 and this works perfectly.
Its like as if the application isn't refreshing or something ? And the build is forcing a refresh ?
Well turns out it was McAfee Virus Scanner !!!!!!!
So annoying, i turned On-Access Virus Scanning OFF and everything worked :-)
Unfortunately the On-Access Virus Scanning turns itself back on after a few hours so I have added Visual Studio and my files location to the exclusion list and this works !
Hopefully someone else will find this useful
I've touched on these issues before, but that was using a system with vs 2005, 2008, vwd, and 2-3 years of associated junk on ;)
Now I'm running a fresh install of Visual Studio 2008, on Vista. I still have some very annoying issues.
The first, is that when creating a new asp.net site, and a default blank page - it won't run. I get a compiler error, the only way I know to fix it is to add a 'codefile' reference to the top of the aspx page. I need to do this for every page - why??
Secondly, I have an issue in that sometimes when opening an aspx page - it basically wont! A new tab is created, but the window inside the tab is not refreshed, it shows the contents of the previous tab (although the design/split/source bar appears at the bottom) - it's as if just that window has crashed.. I can easily go back to the other tabs, but there's no way of seeing the aspx of that file. The file isn't corrupt in any way, and it seems temperamental - but often occuring on old 2005 projects.
Anyone else experienced this behaviour??
cheers :D
Have you installed Visual Studio 2008 Service Pack 1? It fixes several bugs and adds some new features.
Also install the hotfix rollup package for ASP.NET 2.0: April 2009
It fixes a lot of asp.net related bugs.