HI all recently I update my VS to 2013 version. the problem is VS 2013 uses IIS Express to show projects and Rad Grid doesn't show correctly in IIS express. I just don't know why
so I Install IIS itself and try it on IIS and everything becomes OK. I think there is a problem in show telerik component on IIS express.
does anybody have my problem too?
by the way I just write a line of javascript for my grid and on the execution it says there is error in get_dataitems function. but in grids that doesn't have this line of script everything is ok.
I had the same problem.
This fixed it for me. Add
<add key="vs:EnableBrowserLink" value="false" />
to your web.config.
RadGrid Rendering differently in Different Machine of 100% Same Application when opening app in Visual Studio 2013
I am experiencing this 'issue' too. The solution (which is not the best but this one is the only one I know) I used for this problem is installing Visual Studio 2012 next to Visual Studio 2013, so you can also use VS2013 for other projects. Many parts of my website are displaying correctly but mainly Telerik Radgrids causing my problems.
Related
I am using visual studio pro 2012 edition, one of our developers updated the wsdl definitions on a webservice without telling us and for a while i couldnt figure out why the wsdl definitions werent being updated. I did clean and build of the services, stopped the site and even exited IIS Express. Turns out if you have the solution open in visual studio with the old wsdl definition, the new definitions are not updated after pulling latest(svn). I tried several times and the only solution is to close visual studio and restart using the latest codebase.
anyone else experience this? could be a bug in vs2012 only?
I figured out what happened, my colleague copied over the hidden folder .vs folder which had the applicationhost.config file pointing to their username, vs2012 does not give any errors and happily runs the service but it serves the old pages. VS2015 shows an error page which is how i found out the problem.
I've been using custom editor colors for Visual Studio for a few years now, through several versions. I just updated 2013 to Update 4, and now all my colors got screwed up. I reset to the default dark theme to go from there, and I noticed you can no longer change the color of classes and structs, or any identifier for that matter (I use C#). Instead they use the default color. What is happening?
EDIT: This seems to have occurred for VS2012 as well...
I found the source of my problem: Color Theme Editor Extension
It turns out that when the problem occurred I had the color theme editor installed on VS2013 Pro and VS2012 Pro. Even after I disabled it in VS2013, the problem remained in VS2013 Pro and VS2012 Pro and Express for Windows Desktop, so I dismissed that as the cause at first.
What was odd is that it did not occur in VS2013 Express for Windows Desktop. Resetting Visual Studio (any problematic version) to default settings did not fix the problem, it only made it less noticeable. I still had custom fonts and colors from my VS2013 Express installation, so I exported them then imported them into VS2013 Pro.
For anyone else who seems to be getting this issue because of this extension, try installing 2013 Express and re-creating your custom fonts and colors there, and importing the settings back into Premium/Professional/Ultimate. I am not sure if it will work for everyone, but doing that with my previous install worked for me.
I have been having an issue since VS 2012 (currently using 2013) that the panels and windows are constantly all over the place. I have worked with VS for years and this hasn't ever been an issue. I know this has something to do with the .vssettings file but I really don't want to go farting around with it.
I would like something like VSWindowManager PowerToy however that doesn't seem to have been updated since 2006.
Does anyone know how to stabilize the location of windows in panels in VS 2013?
Thanks
There is a VS extension called Layouts O Rama I have been using it for about a week now. and I am very pleased with it, it seems to have calmed down all the window madness I was experiencing with various windows coming up all over creation.
It can be installed using the extension manager Tools > Extensions and updates.
I'm currently working on a project. This project is shared by teamfoundation between colleagues.
I need to change some things in a windows form. But when i open the windows form in the designer, Visual Studio 2012 crashes and does a restart. It gives no errors, ontly that Visual Studio has stopped working. This problem only exist with this specific windows form.
With the same build on a computer of a colleague, it can be opened. My OS is windows 8(64bit) and the OS of the colleague is windows 7 (64bit).
Does this sound familiar to anyone, or is there a way to find errorlogs so i can see some more information?
Thank you in advance!
If you need more information, please let me know!
I'm experiencing the same issue with both VS2010 and VS2012. I found that if I do any form designer work in a VS instance, it is corrupting the designer file when it rewrites it. Currently, my work-around is to do the form designer work using VS2005 then compiling using VS2012. This is not my permanent solution but it's all I have so far. Good luck!
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.