I'm going nuts over this...
I can't add Windows Phone Toolkit to my Windows Phone 8.0 project in Visual Studio 2013.
Nothing works.
Using <toolkit:LongListMultiSelector></toolkit:LongListMultiSelector> on XAML page dishes out:
"The name LongListMultiSelector does not exist in clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
What I did:
Installed Toolkit with NuGet version 2.8.5 (so its over 2.1 as required)
Added "xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit" to my XAML page
Deleted Visual Studio cache in %Temp%, restarted VS... Nothing.
Microsoft.Phone.Controls.Toolkit is present in project References...
It seems like VS is not even recognizing that reference. Toolkit Controls are not present on a list of Controls that can be added to "Toolbox" sidebar.
I desperately need a list with multi selection in my project, and that Toolkit seems to be the only solution...
Finally I solved it... by accident.
I had some other LongListSelector on the same XAML page, with custom ItemDataTemplateSelector, that caused Visual Studio to act strange.
I deleted that LongListSelector (it worked without a problem, so I don't have a slightest idea what was itchy about it for VS) and toolkit reference started to work.
Strange! And so frustrating...
Related
Today I opened a project to find that none of its layouts will render in the designer.
I am pretty sure it is not an issue with my AXML as the app works fine when built. Visual Studio is up to date (15.9.9) and will display layouts in other projects without issue. My layouts are in the correct location (Resources/layout). I have tried -
Cleaning and rebuilding
Deleting the bin/obj folders manually and rebuilding the project
Turning Accelerated Rendering on/off in Options/Xamarin/Android UI Designer
Opening the project in Visual Studio for Mac (7.8) - same issue
Restarting Visual Studio/rebooting my computer
Any ideas on how to fix this would be greatly appreciated. I am not sure what part of the source would be useful to help with answering this question so please ask and I will provide.
Note - this project is on TFS.
This happened to mine and a colleague's Visual Studio a while ago, it was working then it was blank. We tried changing the target framework but couldn't get it working, I even completely reinstalled VS.
In our cases turning off "Enable Accelerated Rendering" in Tools > Options > Xamarin > Android UI Designer worked and we can now see the app as we build it. We didn't change the setting so assume it's the default, which makes me think it was caused by a VS update.
I have often run into this problem as well. Unfortunately, I have not found an easy fix to this problem other than restarting all instances of Visual Studio (and Android Studio if you have that running as well) followed by a full restart of my computer. Hopefully this help, good luck.
I found that the issue was caused by the target framework version of the app being set to Android 9.0. Setting this to 8.0 to match the version used by the designer fixed the issue.
I need the target framework to be version 9.0 and I can't figure out how to add versions to the designer (8.0 is the only one available to me). I have asked another question in regards to this (see here).
When I create UWP or windows phone project and try to edit a page in xaml, no visual changes displayed in the editor - it just stays empty. However, borders of selected element are displayed. So it can be defined that editor processes layout right, but displays no visual part of elements.
The problem occurs on visual studio 2015 proffesional, and also vs 2017 community. So I think problem is not related to IDE, maybe something wrong with SDK.
Hyper-V is enabled if it makes any difference.
Tashiu,
Set the
project properties
->Application
->Target version to Windows 10(10.0;Build 10240),
the design view shows up again.
Hello I would like to use the Apex package on VS2013 but it seems like its impossible.
I really like this design
It looks like its a pivot control like on windows phone but its not allowed for wpf, since im not a pro (still at school) where could i get a control like this for wpf ?
It seems to install just fine for me in a test WPF project in VS 2013. I just right click on my project and went to Manage NuGet, searched for 'Apex' in the online section and clicked Install. What issues were you having?
I have looked everywhere and cannot find a solution. My problem has the following elements:
I have a Visual Studio Solution (Visual Studio 2013) with several projects.
One project ("Control Project") has several user controls I built.
Other projects ("Other Control Projects") contain various open source controls.
Another project (the "Problem Project") references the Control Project and the Other Control Projects.
The Visual Designer toolbox shows the Other Control Project controls perfectly in my Problem Project.
The Visual Designer fails to show the Control Project controls in my Problem Project.
I have tried:
1. Making sure the option to auto-populate the toolbox is checked.
2. Rebuilding the solution
3. Resetting the toolbox
4. Ensuring the access modifiers for the controls are Public.
If I "Choose Items", I can add the Control Project controls to the Problem Project by selected the .exe but this seems like a hack and also has caused other problems that are difficult to define.
Anybody have any clues on what may be wrong with either my Problem Project or my Control Project?
That answer might be a bit late but I recently had the same Problem.
For me it was a Problem with missing DLLs.
I have a nearly simular Soloution like you.
A Library providing selfmade UserControls
Another project ("Problem Project") that references the Control Library
The problem occurred when I recently switched from VS2008 to VS2013 and from .NET Framework 3.5 to .NET Framework 4.5. The cause of the Problem for me seems to be with Crystal Reports references. In my Library project I have a Class that inherits from CrystalDecisions.CrystalReports.Engine.ReportClass. This Class I provide as a control in the Toolbox. When I open the Library Project itself (not as a Subproject) and open a Form to load the Toolbox I got the following Error: Failed to create ToolboxItem of type: CrystalDecisions.VSDesigner.ReportToolboxItem, CrystalDecsions.VSDesigner.
After I knew this I found out, that I have to copy some Librarys, in my case
CrystalDecisions.CrystalReports.Engine.dll
CrystalDecisions.Shared.dll
CrystalDecisions.VSDesigner
to C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE (found it here:Can't add project controls to the Visual Studio Toolbox)
To me it seems like VS Toolbox starts to create the Controls and gets an Error at one of them and stops to fill the Toolbox. In my case the problem might be, that I reference old CR Librarys (v12.x) which work with CLR 2.0 and .NET Framework 2.0 - 3.5 and I compile my project with .NET Framework 4.5 which works with CLR 4.0. It looks like the old Librarys are not supported in .NET 4.x. If I use this Workaround the Toolbox works fine for me.
Greetings
btw. sorry for the patchy english ;-)
I have a project that was created in Blend + Sketchflow preview for Visual Studio 2012.
It is a simple project as I am learning C# and WPF for the first time. I have two windows. A simple start screen with a button that shows the other screen. The other screen has 4 buttons which change colors during a random order animation sequence.
My problem is that the design view became disabled. I can not open any XAML in design view anymore or edit any Storyboards etc. The only thing different I could think of is that I added a class file in Visual Studio 2012. After the project refreshed the design view went away and all I can see is the xml version of it.
If anyone can show me the solution I would appreciate it as I have searched google and stackoverflow and no answers have been found. I am new to both the language and VS/Blend so this may be a simple fix, I have no idea. Thanks in advance!
Make sure your project type is not set to 'console' as Blend will refuse to show design view for this type. If the project type is 'window', Blend will display design view just fine.
Also, Blend for VS2013 will not open a solution file if the target .NET Framework version is set to 4.5.2. A reset of the 'Target Framework' to 4.5.1 (or earlier) and Blend works fine.
I managed to solve this thanks to Surfbutler. My problem was I temporarily switched the project (output) type to console in Visual Studio 2012. When I switched it back to Window the design view started working properly again in Blend.