I saw set of people have the same problem and I tried some it, But I do not know why I still cannot see the design view!!
The output type is Windows Application.
Design view is working properly in VS 2013.
I created this project using MVVM Light Templates; So I do not know if there is a missing stuff in project file.
I also had the same problem until few minutes ago.
I've noticed that Blend 2013 on my PC was supporting up to .NET Framework 4.5.1
But the project on Visual Studio was done with .NET Framework 4.6.1
I changed the Framework to 4.5.1, since that was the latest Blend supports, and that was it. Problem solved.
you can go to
Tools>Options>Documents and in default document view option select which view you liked.
Related
Previously, I would be able to click on this arrow to edit the properties of RibbonControlAdv:
However, after migrating my project to .NET 5, I can no longer see the arrow:
I can, however, see it for the inner buttons:
What could cause this?
It seems this is a known issue and is in fact related to .NET Core. However, it doesn't seem like Syncfusion plans on fixing it as this issue must have been around since the start of .NET Core.
As a workaround, I created a .NET Framework 4.8 project to design the ribbon form, then copied the form over to the .NET 5 project.
I have recently created a rehosted Workflow Designer application and noticed that the UI looks outdated when compared with how it looks in Visual Studio. Does anyone know which could be the problem?
No matter what version of .NET I'm using (for example 4.6 or 4.7), the UI still doesn't update. I have also followed the next article to enable Workflow 4.5 features, but without any success on the UI side.
(WF4.5) Enabling new .Net framework 4.5 features in your rehosted designer application https://blogs.msdn.microsoft.com/tilovell/2012/06/04/wf4-5-enabling-new-net-framework-4-5-features-in-your-rehosted-designer-application
In the rehosted WF application it looks like this:
While in Visual Studio 2017 Community Edition if looks like this (notice the updated colours, icons and toolbox):
Any clues? Thanks!
I followed the following link http://msdn.microsoft.com/en-us/library/aa349641.aspx and found out that my WPF version is 3.0.6920.2011 even though I have already installed .Net Framework 4.5 and Visual Studio 2012. How can that be? I can not write XAML to exploit the new features like Ribbon (cannot find it in the toolbox) with current version of WPF. Thanks.
Right click on References in your project in solution Explorer, choose Add Reference, then enter Assemblies -> Framework, find PresentationCore/PresentationFramework. There you can find version used by your projects.
Note that in some cases - for example if you want to use Ribbon presented in newer WPF, you will have to add suitable reference.
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've moved a C# project from Visual Studios 2008 Professional to Visual Studios 2010 Express.
It converted the project successfully with the VS migration wizard, but the build is failing.
There are quite a few errors, all having to do with the WPF Datagrid. The errors don't occur when built in VS2008. For example:
'DataGridRow' is an ambiguous reference between 'System.Windows.Controls.DataGridRow' and 'Microsoft.Windows.Controls.DataGridRow'
I see that the project also uses WPFTools.dll.
With VS2010 maybe WPFTools.dll is no longer needed? Or maybe I need to use the Professional version instead of the Express version of VS and the project wasn't successfully migrated?
I think I can edit all the places where this is a problem using the full namespace to make the error go away, specifying either "Microsoft.Windows.Controls" or "System.Windows.Controls", but I'm not sure which of the two it was defaulting to under VS2008.
This is most likely tied to the .NET FW version, ie...was this 3.5 prior and you migrated to 4? If so, you would have been using the WPFToolkit prior whereas the DataGrid is now part of the standard FW in 4 and greater.
Remove your references to the WPFToolkit and use the standard FW class and you should be fine.