Recently installed VS 2013 Update 2. I am developing a WPF application and the first thing I have stumbled upon was absence of intellisense. I tried reinstalling, repairing, and any other suggestions found on stackoverflow. Resetting settings, enablig show members in options for text editor did not work.
After a day of frustration I found out that my greed to save space on HDD was the issue - I have unchecked Blend install during setup.
Solution:
Install blend (you can add it as a feature to an existing instalation of VS through same setup)
And after I installed blend, XAML intellisense started working as expected. Hope this saves some time for someone.
Related
I had a warning of Visual Studio stating something about it's going to disable the visual styles because of performance issues.
Because of this I have no styles in my Visual Studio.
I reset al settings but the issue remain.
When loading another Solution everything works as expected, so it's Solution/Project based.
How do I re-enable this?
In Visual Studio:
In Runtime:
I checked in the solution in TFS.
Deleted my files locally and got the latest version back from TFS and everything worked again.
Another 3h wasted.
I had the same issue again today, and I found right the solution to the problem:
I cannot get XAML Edit & Continue (WPF) working.
I have Visual Studio 2015 Update 2, so it should work as mentioned here:
https://blogs.msdn.microsoft.com/visualstudio/2016/04/06/ui-development-made-easier-with-xaml-edit-continue/
However, after any change in XAML source (font size, colors, directly or in resource,...), change is not applied real time.
I am on Windows 7, latest .NET Framework. I must be missing something.
OK, I found this in a comment from Dante Gagne (Program Manager # Microsoft) from the link in your question.
I have VS2015 Professional Update 2 and was wondering what was going on.
I apologize for the confusion. Edit & Continue is ONLY available in the Visual Studio “15” Preview. The feature is one that we’re still working on, but we didn’t feel was ready for the “RTM” branch yet. That means that Edit & Continue will not work in Visual Studio 2015.
Additionally, if you are working with a Universal Windows Platform
project (UWP), you need to be using the Windows Insider build 14295 or
later along with the Windows Insider SDK build 14295 or later.
If you’re meeting this criteria and still can’t get it to work, PLEASE
get in touch with me and I’ll see if I can help.
His contact details are in the link from your question.
Posted again here
Update 6/23/2016
Visual Studio 2015 is going to have an Update 3 after all. However, As of the current RC, I do not see any plans for xaml edit and continue. See Visual Studio 2015 Update 3 RC
Update 8/12/2016
As Legends mentioned in his comment VS2015 Update 3 does NOT have XAML Edit and Continue. Looks like we're going to have to wait until VS "15" is released. I'll update again if I see Microsoft put a release date out.
Update 5/10/2017
VS2017 is out and I believe that is the version where this is supported. Probably no more updates from here on out.
Another couple reasons :
You may be in a Release build. It will let you edit but won't apply changes due to optimizations.
Your installation may be corrupt. If you don't see XAML listed under Text Editors - that could be the sign of an incomplete install.
See VS2017 RC1 Installation installation error - Microsoft.PortableLibrary.TargetingPack.Msi failed - No XAML
for more details on how I fixed a corrupt install.
Make sure you're not just being stupid and accidentally reopening the old VS2015 after a crash too :-) They look very similar.
I need to create a WPF app using the Surface SDK. I am using Visual Studio 2012, and according to this SO post, VS2012 doesn't allow that. However, since this was posted before it was officially released, I want to make sure I'm not missing something.
I just need a few of the touch/swipe controls that come with it. Is there a different option for VS2012? The other developer is using 2010, so it needs to be able to still run on his machine. It's a very simple app that I just need to hammer out, so I'm looking for the fastest, easiest method. Both of us and the end application is to run on Windows 7.
I found an easy solution by which it seems to work. It does expect you to have Visual Studio 2010 installed. Following the following steps I managed to compile in Visual Studio 2012 using .NET 4.5. TouchDown events work. I tried it out on some small projects and they seem to work perfectly fine.
Use Visual Studio 2010 to set up a Surface project.
Safe and close Visual Studio 2010.
Open the solution using Visual Studio 2012.
Change the target framework under project settings to .NET 4.5.
Save as a new solution file.
Compile, ... everything works!
This method prevents you from having to set up all the configuration files/references yourself. The only downside is you don't have any of the Surface tools integrated into the IDE. E.g. the toolbox, project templates, ... This of course doesn't prevent you from writing plain XAML yourself.
If for some reason this doesn't work in the long run I will update this post.
The easiest way will unfortunately be for you to run VS2010.
Currently the SDK is not supported in VS2012, for a few reasons.
Notably, the way that touch works in Win8 is a lot better than in previous versions of Windows. This unfortunately meant a rewrite of the touch layer that the Surface SDK uses. The new controls are written to adapt dynamically based on mouse/touch input, making the Surface SDK controls a bit redundant.
Microsoft might make the SDK available for VS2012 in the future, but this is kind of debatable.
If you are still dead set on giving it a shot, download an application called Orca (http://msdn.microsoft.com/en-us/library/windows/desktop/aa370557(v=vs.85).aspx) and edit the SDK installer file, removing the dependency on VS2010.
This is how I got the Surface 1 SDK to work with VS2010, since it was targeting VS2008 (note that it still has not been updated to work with VS2010)
Let me know how you go.
I am trying to get started doing some Silverlight development. I am interested in learning about the out-of-browser support. I can create and run Silverlight 3 applications just fine. I have confirmed that I have Silverlight 3 instead of Silverlight 3 Beta. I have been able to confirm this because my API list includes Application.InstallStateChanged instead of Application.ExecutionStateChanged.
However, I do not have the option to enable my application to run offline in Visual Studio. I can see this option in this blog post (http://johnpapa.net/silverlight/updated-silvertwit-code-for-msdn-magazine/). Unfortunately, I do not have the option shown or the Reduce XAP size option. I have downloaded the Visual Studio tools from here (http://www.microsoft.com/downloads/details.aspx?familyid=9442b0f2-7465-417a-88f3-5e7b5409e9dd&displaylang=en).
What am I doing wrong?
Thank you!
It looks like John Papa is using a new version of visual studio possibly the VS2010 beta.
Try this tutorial instead
http://wildermuth.com/2009/03/18/Enabling_Out-of-Browser_Support_in_Silverlight_3
or
http://blogs.msdn.com/katriend/archive/2009/07/10/silverlight-3-out-of-browser-applications.aspx
Corrupted Install
It looks like a corrupted install. Try uninstalling and then see Allen Chen's advice here:
http://silverlight.net/forums/t/83226.aspx including:
Silverlight3_Tools.exe /x:c:\temp /u to manually extract the SL 3 files and c:\temp\SPInstaller.exe to verify the tools install.
Use Blend
Also, If you have Blend 3 installed (preview here) you can enable Out of the Browser inside of Blend. See Project->Silverlight Project Options.
One thing might be that your Silverlight developer runtime got corrupted/overwritten. Try installing it once and see if it solves...
http://silverlight.net/getstarted/silverlight3/default.aspx
Just downloaded the Silverlight 3 Toolkit and executed the MSI file.
Now I need to reference the Microsoft.Windows.Controls.dll file but don't know where MSI unpacked it. Can't find it at C:\ or in C:\Program Files. Where might it be?
ok, this post says that all the components should be in the toolbox, e.g. DockPanel, they are for Visual Studio 2008 Professional but not for Visual Web Developer 2008 Express (it has some controls but not DockPanel for instance)
Answer:
Ok, the answer is: reboot and restart everything (until then Silverlight got a AG_E_PARSER_BAD_TYPE error, and brought down both Visual Studio versions and Firefox). After restarting everything, it works fine: the controls are automatically in the toolbox so you just have to drag them in, no need referencing the dll anymore as in Silverlight 2.
It didnt automatically add anything for me for Silverlight Beta 4 Toolkit and Visual Studio 2010 Beta 2.
I followed these instructions. My toolkit bin was located :
C:\Program Files\Microsoft SDKs\Silverlight\v4.0\Toolkit
In addition I had to select additional DLLs for additional toolkit items from those described in the article. I also had to check the checkbox to indicate I actually wanted those items.
There must be a better way! Anyone?
Just in case anyone was wondering, I was :-).
There is a start menu group named "Microsoft Silverlight 3 Toolkit March 2009" with all the relevant info. The toolkit assemblies can be found in "C:\Program Files\Microsoft SDKs\Silverlight\v3.0\Toolkit\March 2009\Libraries"
The July 2009 release of the Silverlight Toolkit added a "Open the welcome page" choice at the end of the MSI setup.
The path names for the July release are also slightly different, but using the Welcome page (a link is also added to the Start Menu), you'll always have a quick method to find 'em.
Checking that box will make sure that a page opens up with details about everything that's installed, including links to all the binaries, themes, the documentation, etc.
Also, since the controls are all referenced through the AssemblyFolderEx registry key, you can add a GAC-style reference in your C# or VB.NET project...
<Reference Include="System.Windows.Controls.Input.Toolkit" />
And that will just work when built on a machine with the Silverlight SDK.
Hopefully it's a step in the right direction.