I currently use Visual studio 2010 and it is very slow in design view when a page has a lot of controls. For example changing a property on a control in a big page can show the spin wheel (hourglass) for 5 to 10 seconds!
I heard that VS-2012 was faster but will it be faster in this particular case? I'm ready to upgrade to VS-2012 if it will improve the speed in design view.
Does someone here made the switch to VS-2012 and saw a speed improvement in design view?
I'm running a i7-8gb with Windows 7 64 bits.
I have found the design view quite a bit faster with XAML and WinForms, so I would guess there were also improvements made to the ASP.NET designer. YMMV.
Related
Since a while I noticed an odd and very annoying lag when switching between the xaml view and the designer space in Silverlight apps (ie. changing the keyboard focus by clicking into the respective other space). The duration varies but sometimes Visual Studio freezes for seconds on every such switch, which is frustrating.
Interestingly, this is only happening as long as the file in question has unsaved changes.
I have some extensions installed, for example the DevExpress toolkit and an older .NET Reflector.
I'm not entirely sure when it first happened, but I believe I didn't always had this after I switched to Visual Studio 2012 - certainly not before with 2010.
Anyone got a clue what might be triggering this and how to stop it?
I know it sounds a bit off, but I found the culprit to be RIA Services.
Switching between the designer and the xaml view is never instantaneous, but the presence of the auto-generated RIA Services code makes it slower from slightly more annoying to outright offensive, depending on how complex the project is.
Luckily this is easily fixed by having the auto-generated RIA Services code live in its own client library, which is considered best practice anyway.
I wonder what's going on behind the scenes that causes RIA Services to have that kind of influence on the development environment.
I am using the 2010 version of Visual Studio, but am having many problems with delays - my computer has a good configuration of RAM, and processor - especially when saving files.
Currently I am carrying a medium-sized project, only one open file (ASP.NET page) using a single suite of components from third party, the Telerik. And yet, in time to save, or modify the tab, the entire IDE is slow. I know there may be several factors for this problem, but I'm not carrying the computer (the problem apparently is the memory management on behalf of the IDE).
Does anyone know any way to improve it? Change settings, Windows services. Oh yes, I'm using a plugin to modify the color of the IDE and another to find (Ctrl-click) the object reference.
Memory Initialization:
Memory: 280000K
Virtual Memory: 350000K
Have you tried disabling all the plugins and make sure that it is VS that actually causes the slowdown?
I have Resharper installed and VS can be slow sometimes. I turned it off (suspend on v5), and VS is back to blazing speed. Of course, inversely coding productivity is impaired by not having Resharper.
There are many causes and circumstances that can lead to what you're describing. So I'd better recommend you to check the links bellow...
VS.Net 2010 IDE Very Slow
VS 2010 very slow
VS 2010 slow for edit of first file in project with many web references
VS2010 C#: Delay when opening a file inside IDE
I'm a Silverlight newbie. Just downloaded version 3.0 after the Mix announcement. I'm running VS 2008 SP1. When I select a design element in the preview pane or in XAML, the properties window is disabled and displays
Property Editing Not Available
I can open the solution in Blend and have no problems with it's property editor. So within Visual Studio, I'm forced to enter everything in the XAML pane and rely on Intellisense.
Is something wrong with my installation or environment? Or am I supposed to switch back and forth between Expression Blend and Visual Studio (I can't believe that should be the case).
There is nothing wrong with your installation or environment. The XAML designer/editor in VS2008 is very limited in what it offers for XAML editing whatever the version of Silverlight, being really just a rendering engine at the moment.
Expression Blend is the visual editor of choice for now - there are 3rd party editors available (such as XAMLCruncher and Kaxaml) but they don't really support XAML with code-behind classes.
Additionally the Blend 3 preview that was released to support SL3 seems to have a few improvements which address previously inferior experience of directly editing XAML in Blend (notably IntelliSense).
I had the same problem with Visual studio 2010 and Silverlight 5.0. It was intermittent.
One thing I found to help is to switch the XAML page to show Design view and then switch back to Code view or vice versa. If you have hybrid view, just temporarily switch.
I did that and it just worked fine. I do n't know the reason it worked but it did.
Is something wrong with my installation or environment? Or am I supposed to switch back and forth between Expression Blend and Visual Studio (I can't believe that should be the case).
You'll find you need to do that a lot for both Silverlight and WPF if you want to make full use of the UI controls.
I find VS incredibly slow and clunky for designing and rendering XAML and much prefer Expression. Switching between the two is no big deal as really one's for code and ones for design.
I haven't download the Silverlight 3 Beta yet, but the Silverlight 2 designer intergration in visual studio is very poor.
VS 2010 is suppose to have better support for XAML Editing in WPF and Silverlight. So for now, you'll have to find the right balance between Blend and VS.
SilverLight 3.0 beta just shipped. VS2008 SP1 shipped last year. It would be surprising if it supported SilverLight 3.0 out of the box, and more suprising if the VS support that ships with SilverLight 3.0 beta were not "beta" quality.
If you find problems, then be certain to report them to Microsoft.
I have heard several podcasters (most recently the guys on DotNetRocks) say that the look and feel of Visual Studio 2010 has been completely redesigned and Visual Studio rewritten in WPF.
I have been watching some demos on channel9 of the Visual Studio 2010 CTP and the only thing that looks different to me is the opening screen.
I read the notice on MSDN, but it doesn't say anything about the look/design of Visual Studio.
Has Microsoft reversed direction on this or are there going to be major changes made to UI of the final product?
I'm guessing 3D with a space theme. You'll be able to "fly through" your code, "orbiting" classes, "shooting down" bugs and "launching" your code.
It's way too soon to make guesses about what it will look like: I don't even think that they know what it will look like.
However, from what I've heard, they are in fact rewriting portions to be WPF/C#, but they are not throwing everything out and starting from scratch. Instead, they will be rewriting portions as it makes sense. For example, I saw that they have some new UML tools that definitely look to be done in WPF.
Uh, the beta has been available for over a month. I have been playing with Visual Studio 2010 on and off. It is very similar to 2008 in overall design.
You can download it here and see for yourself where they are taking the product:
Download Page at Microsoft.com
There are a metic ton of videos on Channel9 about VS2010, TFS 2010 and then the PDC 2008 sessions online as well. They are also starting a new series called 10-4 dedicated just to VS2010 - a walk through of sorts.
Let's pray that they don't dink with anything, visually. My #1 guess is that they'll try and wrap the new office ribbon bar around our necks. ;|
I've heard that its going to have a historical debugger.
Also- this should prob be a wiki
From WPF Wonderland:
Visual Studio 2010 gets WPF facelift
WPF has been out for a couple years. That’s long enough that new releases of Microsoft products are sprouting WPF interfaces.
Last year at PDC Microsoft announced that the code editor in Visual Studio would be re-written in WPF. Microsoft didn’t stop at the code editor though. Today Jason Zander, GM for Visual Studio, revealed the new WPF based IDE.
Highlights from the PDC Keynote #1 on Day 2 (see: PDC website)
Multi-monitor support for the IDE via
WPF.
Building classes from test classes.
Toggle TFS bugs over a code segment
in Debug mode.
Partial config files for debug,
release.
WYSIWYG Silverlight Designer.
OK, so see questions like this one and this one and the question I have is - does one have to use Expression Blend to do Silverlight development or can any of it be done with just Visual Studio? (2008, in this case)
I haven't gotten started using Silverlight yet and through my workplace's MSDN I can get Expression Blend without any issues, but for my side work, do I have to drop the $499 for Expression Blend 2? (I know there's a trial but I'm thinking beyond that)
Obviously I'm concerned that in order to get into Silverlight development there's a huge financial investment involved and I already own Visual Studio 2008 - is it possible to do development without Expression Blend or would that just be impossible?
You can do everything in Visual Studio. But then again you can do everything in Notepad as well... it all depends on how much the given tool will help you along in the process. Having Blend will be a great asset from a design point of view but wont really do much for you in terms of programming the application. Download the trial and see how it works... if it adds value and saves time then it's well worth the purchase.
I've heard rumours that since there is no Expression Blend Express or Expression Blend Light that there will at least for a while always be a version of Blend in a "Preview" state and the next one will come out before the previous one expires.
That being said, it would be hard to bet your business on something like that. There are third party tools like Kaxaml that can do some of the things Blend can do and I wouldn't be surprised to see more to fill this niche.
You can do it in Visual Studio 2008 and it will work. The issues that I have come across in trying to only do Visual Studio is that I find I can do things a lot quicker in Blend than I can in Visual Studio. The visual designers are different enough that, depending on what you are going to do, you may find yourself using both environments.
If you are doing just small projects, and not a lot of UI components, then you can get away with just Visual Studio. However if you are doing a lot of design work and UI is important to you, then I would recommend geting the entire expression studio as you will find yourself using Blend and Designer.
It quite is possible. If you don't care too much about the eye candy.
Blend is more of a designer's tool than a development tool.
You could try the Microsoft Action Pack Special edition for Web Solutions if you are at least a Microsoft Registered Partner.
And now you can even use Eclipse. :)