Visual Studio 2017 Xaml intellisense not working with tag "Style" - xaml

I have Visual Studio 2017 rel. 15.4.2 with Xamarin 4.7.10.33 (s.o. Windows 7 64 bit).
I create a simple app for Android and iOS and I try to use styles resources.
When I try to define a style inside a ResourceDictionary (in Application.Resources), the intellisense do not show tag "Style".
I have to insert it manually and I don't see nothing oh style's properties.
I see only this
How can I solve this problem?
Thanks in advance

I can reproduced this in my side and I have reported it to the VS Product Team to seek for a better support, please check this: Visual Studio 2017 Xaml intellisense not working with tag “Style”
and you can add your comments and vote it, then you can get any updates from the VS Product Team engineers to know the detail progress.

Related

Reporting template in Visual Studio 2017

The Reporting template seems missing in VS2017 (I am using Visual Basic). Any way to get it back?
I have already tried installing SQL Server Data tools and the rdlc extension from the marketplace, but it still doesn't show up.
The template is available in the Add New Item window. Select Visual C# and then look for the Report and Report Wizard templates. These templates are only visible under Visual C#, not under any subitem.
Try updating ReportViewer to version 14.0.0.0 and installing Microsoft.RdlcDesigner. This worked for me for Visual C# and then just like J.Bunch said there is no sub item Reporting like there was before so you just scroll down thorough all items. Also try this although the example is for C# I think it should at least help you with VB.Net as well. Hope it helps.

Visual Studio 2013 update 3, Designer won't load

I have the following situation. I installed Visual Studio Update 3 last night. Now I have a problem that when I open my projects (Universal Apps) which i have done while i had update 2, my designer won't load and it throws an exception:
Does anyone knows how to solve this? I guess this is not a bug because probably everything was tested by Microsoft, and this is not RC update. Im about to delete this update if i don't figure out the solution. I'm guessing that it might have to do with xaml if anything changed?
I figured out from the connect bulletin that there are two folders in your Windows profile that need to have their contents cleared out in order for the Visual Studio designer to work with Visual Studio 2013 Update 3.
The two folders are:
For Blend: AppData\Local\Microsoft\VisualStudio\12.0\Blend\ShadowCache
For Visual Studio 2013: AppData\Local\Microsoft\VisualStudio\12.0\Designer\ShadowCache
Don't delete these folders, just delete the content of those folders and you will be back to working happily with the XAML designer again.
Clearing the ShadowCache did not resolve this for me. Found a clue from an MSDN article and checked the event viewer for exceptions, look for XDesProc.exe.
The problem was an out of date driver for my graphics card.
Once that was updated all started working again

I upgraded a Visual Basic 6 project to Visual Basic 2008 project and got unknown errors

I've recently upgraded my project to Visual Basic 2008 and I'm getting the following errors which I cannot identify, I hope someone can help:
AxThreed.AxSSCommand is not defined
AxActiveInput.AxSSDropDownEdit is not defined
AxPVTEXT3DLib.AxPVText3D is not defined
Any idea what this is and how to fix it?
It looks these are references to 3rd Party ActiveX controls. ActiveThreed, Protoview Date Control, etc
You may need to Add/Re-Add the relevant control to your project. Right click on the toolbox so select the items to want to use. If you don't see them in the list to may need to register/re-register them on that machine
Have a look at this page for more info: http://msdn.microsoft.com/en-us/library/ms973200.aspx
Number 3 here seems to indicate how to fix the problem... I believe some of your controls are not loading.

Is it possible to create a generic base class for user control in XAML for Visual Studio 2012

There seems to be a bit of yes/no/absolutely/no way info floating around on the web about this. I'd like to be able to create a base class.
class GenericUserControl<T> : UserControl {
// Lots of cools stuff based on T cause I wanna! In fact T
// will be the ViewModelClass but please no pedantic discussion on what
// MVVM is or is not. I want generics in XAML!
}
Then create a new concrete user control in the designer based off GenericUserControl
class MyControl : GenericUserControl<MyControlViewModel> {
}
I've seen a number of blog post claiming this is possible using x:TypeArguments in XAML and there seems to be XAML doc http://msdn.microsoft.com/en-us/library/ms750476.aspx suggesting this feature is possible but then again I've found posts saying this feature is broken in Visual Studio 2012.
So if this is possible and any genius can figure out how to get it working specifically with VS 2012 then please post a tested solution here and I will be super happy.
This is possible to do using x:TypeArguments in xaml, but it is known to break the various xaml designers (both inside Visual Studio and Blend).
The problem has been fixed in the Visual Studio 2012 Xaml designer, with the latest CTP of Visual Studio 2012 Update 2.
Discussion:
http://social.msdn.microsoft.com/Forums/en-US/toolsforwinapps/thread/895b38c7-ddde-4d38-8915-493be0efe6a7/
CTP download:
http://www.microsoft.com/en-us/download/details.aspx?id=36539
Unfortunately it does not seem to work in the latest Blend for Visual Studio 2012.

Intellisense not working for XAML in VS2012 and only partially in Blend

I'm trying to get RC of Visual Studio 2012 working for XAML files. I can't seem to get any XAML Intellisense and the option within Tools is greyed out.
I've also tried to run the solution using Blend, however I only get Intellisense for custom controls such as telerik then.
When ever I drag controls onto the design surface I get an "Object reference not set to an instance of an object" exception but the control is still added to the surface.
I've read that this was a bug within VS11 and was fixed with in the Visual Studio 2012 RC.
I've created a new Silverlight Application and the intellisense is working so i'm wondering if its an issue with how my projects are set up.
I have all of my Styles within a separate themes project, which is referenced by other all other projects. Within the designer these references show up as errors but when the application runs they are resolved fine.
Would unresolved resources at design time affect Intellisense?
Click "Build -> Clean Solution", then "Build -> Build Solution". ("Rebuild Solution" alone doesn't work.) [Source]
If you have a reference to any of the expression blend dlls for interactions and you are using silverlight5 you will need to update the following dlls:
Microsoft.Expression.Controls.dll
Microsoft.Expression.Effects.dll
Microsoft.Expression.Interactions.dll
System.Windows.Interactivity.dll
Blend + SketchFlow Preview for Microsoft Visual Studio 2012
http://www.microsoft.com/en-us/download/details.aspx?id=30702
Ref Location:
C:\Program Files (x86)\Microsoft SDKs\Expression\Blend\Silverlight\v5.0\Libraries
Exact same problem here, using WPF.
In my case, removing:
<Page.Resources>
<vm:AnyViewModel x:Key="anyViewModel" />
</Page.Resources>
Solve my problem...
One known cause of XAML Intellisense failure is if System.Windows.Controls.Toolkit is one of the project references. I've seen where deleting that reference instantly fixes the problem. The problem is described in the comments of this Connect bug for VS2012 Beta, but it applies to the RC with the July update as well.
I've found that some xaml designers for a control have this issue, where other controls are just fine.
The problem (in my case) seems to be if parameters are null or events call uninitialized singletons. Something the designer gives you a stack trace and other timers renders with no problem.
I've found by changing the back-end code for pages that don't have Intelli-sense to include DesignerProperties always fixes the issue (in my cases).
public Homing()
{
InitializeComponent();
if (DesignerProperties.GetIsInDesignMode(this))
return;
// some other code here that may have uninitialized members
}
t
I'm not sure if I had the same problem, but Intellisense mysteriously stopped working for me within a XAML file. I tried cleaning the build as someone suggested, but that didn't work.
After I restarted Visual Studio 2013, the Intellisense in the XAML page started to work again.