We are currently building a WPF solution in Blend 3 and Intellisense is extremely slow.
Visual Studio 2008 and 2010 beta 2 do not have any problems, Blend 2 did not have any issues either.
How would it be possible to disable Intellisense in the XAML editor.
Many Thanks,
KShaban
What was actually causing the problem for me was that my UI project had a lot of external assemblies referenced. Specifically, it was referencing some DevExpress Winforms stuff for reporting needs.
Once I refactored the UI project to not depend on those dependencies Blend started working great.
As a note, I attached a debugger to Blend while it was hanging and it seems that Blend keeps re-reflecting over those same assemblies. Also, the assemblies in question were not in the GAC.
The funny thing is VS2008 or VS2010 do not choke at all as far as intellisense on the same project.
Hope it helps.
Related
My question is similar to others, but my particular nuance of this problem doesn't appear to have an answer I can find on here so far, so here goes. (edits in italics)
Our company has a deployed application written in VB6. Since VB6 development is no longer officially supported in Windows, our company made the decision to port our VB6 application to VB.NET.
(Prior to this edit, I had mentioned that the project was converted to VB.NET using VS 2015. This was incorrect, I discovered that my coworker had actually performed the conversion using VS 2008, and I was working on the 2008 project in 2015.)
So we are now working with the VB.NET conversion in VS2015. As many of us know, the VS 2008 converter does an incomplete job porting VB6 code to VB.NET code so there are many, many errors to sort through (as of this writing, all compile errors are fixed). In particular, though, I'm trying to open the various forms for the project in the Designer so I can see and work with them. The designer specifically is reporting the error:
Could not resolve mscorlib for target framework '.NETFramework,Version=v2.0'. This can happen if the target framework is not installed or if the framework moniker is incorrectly formatted.
I saw some mention of a 256 character limit on dependency paths. This dependency is met in my case. I have also confirmed that .NET Framework 2.0 is installed and active in my instance of Windows. I have seen the recommendation to upgrade the .NET Framework version as well, which was successful in itself but did not resolve this mscorlib issue.
Full call stack for this error follows:
at Microsoft.VisualStudio.Shell.Design.VsTargetFrameworkUniverse..ctor(IDesignTimeAssemblyLoader assemblyLoader, IVsDesignTimeAssemblyResolution projectAssemblyResolution, IVsSmartOpenScope dispenser)
at Microsoft.VisualStudio.Shell.Design.VsTargetFrameworkUniverse.GetUniverse(IDesignTimeAssemblyLoader assemblyLoader, IVsDesignTimeAssemblyResolution projectAssemblyResolution, IVsSmartOpenScope dispenser)
at Microsoft.VisualStudio.Shell.Design.VsTargetFrameworkProvider..ctor(IVsDesignTimeAssemblyResolution assemblyResolution, IDesignTimeAssemblyLoader assemblyLoader, TypeDescriptionProvider parentProvider, IVsSmartOpenScope openScope)
at Microsoft.VisualStudio.Design.VsTargetFrameworkProviderService.get_TargetFrameworkProvider()
at Microsoft.VisualStudio.Design.VsTargetFrameworkProviderService.GetProvider(Type type)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.GetType(String typeName)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.System.ComponentModel.Design.Serialization.IDesignerSerializationManager.GetType(String typeName)
at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)
How can I gain the ability to view my project in the Designer?
As far as I know, opening VB6 files in VB.NET will not work. You will have to make modifications in Visual Studio 6.0 or re-write the application in VB.NET/C#.
Older versions of Visual Studio (until 2008) had some converters but they never really worked as expected.
You can take a look at Visual Basic Tools for Visual Studio, it "allows to work with classic VB workspaces and projects within Visual Studio.", this will allow you to modify the VB6 project in a newer version of Visual Studio but the code will remain VB6.
Regarding your exact issue, others have reported that the following worked for them:
Remove and add back project references that have warnings.
Rebuild the project
Remove and add back Microsoft.Office.Core
Good luck!
As someone who has converted a number of VB6 applications to VB.Net, I always advise a full rewrite. The languages are just too different. You waste far too much time trying to resolve issues of this type.
Better still, just leave the VB6 application running as is.
Microsoft's VB6 support statement
I have Visual Studio 2015, but can't get the new VB language features to work. Or to show up. It's like the product came without it. The null-coalescing operator doesn't work, read-only auto-properties aren't allowed, etc. This is true even when I set up a brand new project, targeting any version of the framework (which shouldn't matter, but I'm trying everything I can think of).
I've got Resharper 9 installed. Following a suggestion in this question, if I select the project, the VB Language Level dropdown list doesn't show anything more recent than "Visual Basic .NET 12".
There are no LangVersion tags anywhere in the .vbproj files. If I add them it seems to make no difference.
I was under the impression that you didn't have to install anything separately for VB 14, just use VS 2015 and you'll have it (C# 6 actually is available and working in C# projects) but it's not there.
Anybody have any ideas what else I can look for?
It's Resharper.
I'm using Resharper 9.2 Ultimate. Resharper is what's putting all the error messages into the code editor. If I suspend it, all the problems go away, and the code compiles and runs exactly as it should.
I should have taken a cue from the fact that the VB Language Level isn't showing the latest version of VB.
Off to contact technical support.
I have a problem with Visual Studio 2012 that I'm hoping someone can help me out with.
Visual Studio hangs when I try to modify a XAML file. Admittedly my solution contains over fifty projects and I am running ReSharper and StyleCop. This is my first day in a new job and my first experience with XAML so I'm trying to make a good impression!
What can I try to sort out this issue?
Thanks in advance, Mark
After a bit of googling, I found the solution to my problem here: http://weblogs.asp.net/fmarguerie/archive/2009/01/29/life-changer-xaml-tip-for-visual-studio.aspx
Try to suspend/uninstall Resharper and all other plug-ins for Visual Studio. This worked for me whereas all other methods did not.
Also try to run VS with /SafeMode flag and see if it works properly.
This is still issue in 2013 (as of May 2016). The suggested solution above is not helping.
With my Visual Studio 2012.4 I found that while opening XAML in design mode, XDesProc was using 2gb of my RAM and 25% of CPU (i7 8 core), I resolve the problem by turning off the data loading in View Model’s constructor if in design mode. Loading the ItemsSources of my many Comboboxes just bogged down the designer. This way I can still have my designer. Don't forget to import System.Windows and System.ComponentModel in your ViewModel and add these code below in the constructor
If DesignerProperties.GetIsInDesignMode(New DependencyObject) Then
‘ Do nothing
Else
‘ Load the data
End If
Anyone know of any examples on creating plug in's for VS2008 - preferably with VB.net?
If you can wait for VS2010, it should be lot easier because of new extensibility framework they use (MEF). Basically the extensibility hooks are now managed and are very decoupled.
Otherwise, I know this framework. I have never used it.
Or you can use the "Visual Studio Add-in" project template included in VS2008 ( File > New Project > Other project types > Extensibility > Visual Studio Add-in). It is hard to learn and debug, but it works.
Finally, if it is for internal use, you can just create simple VS macros that reference normal .Net assemblies. This is how I do internal extensibility projects because there is zero friction. You just create small macros that call your assemblies (to show a Windows Forms dialog for instance). Then you add that macro to VS toolbar or define a keyboard shortcut for it.
I hope this helps
I don't mind learning xaml and I'm sure I need to be familiar somewhat, but when I was first trying out Silverlight 1 with javascript it looked like a tremendous amount of overhead. I decided to wait until tools matured and asp.net was added. Well, asp.net has been added with Silverlight 2.0, and now I want to look at using it. But, xaml, to me, still looks like a lot of work for each small step. My experience with Flash seemed a lot more simpler for the graphics side of things (never liked ActionScript that much.) Will $500 for Blend take care of much of my xaml concerns? Can I use Visual Studio Express with the full version of Microsoft Expression Blend?
Do I need Microsoft Expression Studio 2?
Thank you.
Just as a profressional web developer can't lean on Dreamweaver's drag-and-drop to avoid learning HTML, you should climb the XAML learning curve.
Blend will still help, however- just as many started up the HTML curve by doing some drag-and-drop and studying the resulting HTML code. I did some prototyping with Silverlight 1.1 and Blend helped significantly in my understanding of XAML. It helps to have a "real" project to work on, even if it's a proof of concept. Concentrate on the containment paradigm between Canvas and other elements and you'll pick it up quickly enough. I wouldn't worry too much about the MPATH stuff, do rely on the tool for that.
Microsoft Expression Blend takes care of a lot of XAML for you and helps you create animations and setting up triggers (XAML triggers). I would hate to have to do all that by hand coded XAML. I have not used Blend with Visual Studio Express but I believe it will work just fine. Microsoft Expression Blend 2 uses the sln file to open a project.
Expression Blend will not help with databinding. VS2010 promises databinding in its WPF designer, but if you can't wait until then, look to learning some XAML.
Count XAML as one of the many new .NET 3.5 things to learn when working with WPF/Silverlight. I recommend Pro WPF in C# 2008 from APress
Expression Blend give you the ability to draw shapes, paths, Union or diff shapes, create animations (similar to Flash Tweening), wire up simple triggers (like on mouseover play an animation). All with out having to dive into XAML.