When can we expect XAML 2009 support in the tools like Expression Blend 4, Visual Studio 2010? Has Microsoft mentioned something somewhere publically? Willl we have to wait for Blend 5 and VS 2012?
I don't think Microsoft has mentioned this, from my understanding you can use it in WPF if you use loose Xaml files, but no designer support.
Related
I already installed Visual Studio 2013 Professional version, then I download the Crystal Reports Runtime from the SAP site from this link
http://scn.sap.com/docs/DOC-7824
the problem now that I focus is when I go in VS to Add Item>> then I can not find crystal report item there even in Add/New Item/Common Items/Reporting
It is the same question asked in this link Crystal Report in Visual Studio VB.NET 2013 but there is not an answer
What is the problem and what is the solution?
Thank you for any suggestion
Maybe a odd answer,
But after testing and trying multiple reporting generators
Microsoft Reporting
Syncfusion Reporting (looks a lot like MS Reporting)
Telerik Reporting (just try it)
Crystal Reports (very poor support and compatibility with newer Visual Studio versions)
Microsoft Word (al lot of coding, but most flexible)
PDF
I came up with 2 favorites.
If you can't afford to spend USD 500 for Telerik Reporting, I suggest stick to Microsoft Reporting.
In short, ditch CR and look for a better solution.
;)
WPF never ended up supporting XAML 2009, which is a shame because it added some useful extensions, such as generic type parameters and complex x:Key values.
UWP seems to have built upon WPF. Does it, or anything else in .NET 4.6/Windows 10 support XAML 2009, six years after the fact?
The situation in 2018:
For UWP, the answer is no. It's built over XAML 2006.
For WPF, the answer is mainly no. You can in theory use it but with big caveats.
For anything else, the answer is yes: Xamarin.Forms is XAML 2009 based.
The big question mark is XAML Standard. We haven't heard from it for a while and I think it was presumed that it's going to be XAML 2006 based because WPF and UWP are. You might find the following (open) GitHub issue interesting: Use XAML 2009 as the basis for XAML Standard
Is there way to use the Extract Interface refactor option when in VB.NET?
I've noticed that Refactor does not show in the right-click context menu when in VB.NET.
Since VS 2005 Microsoft has had a deal with DevExpress to offer free refactoring tools for Visual Basic. For VS 2005/2008 look for Refactor!, for newer versions try CodeRush Express.
In VB.net 2015, use Edit > Refactor > Extract Interface. This functionality has been added.
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.
Is it possible to get the same level of syntax highlighting in Visual Studio 2008, that SQL Server Management Studio has? This is regarding T-SQL.
For example SSMS has separate highlighting options for operands, system functions etc, while Visual Studio 2008 only seems to have one 'keyword' for T-SQL.
Not sure if this is what you're looking for but someone did come up with an app that will take your VS color settings and convert them over to ones that will work in SQL Server Management Studio. You can find the post about it here.
See this: related question
To get a better level of control you will have to write an addin and a parser, both of which are very tricky.
VS 2010 will have MEF and WPF which means that writing addins which change the visuals will be significantly simpler.
If you are looking for a simpler framework to write this kind of stuff in VS 2008 have a look at DXCore.
I use SQL 2008 and VS 2008 DB Pro edition. And what I often do is writing SQL in SSMS and copy & paste to VS.