I want to create an app with Material Design using Xamarin and Visual Studio. I want to achieve this using the v7 AppCompat library, so my app runs well on older devices.
I have an activity with a toolbar and a button.
But in the Visual Studio Designer the layout isn't as it's supposed to be(No Material theme and no Toolbar):
But the strange thing is that it runs properly on my phone(without any changes made):
How can I fix this?
This functionality is slated to be released in our Cycle 8 release(XVS 4.2.0.378 at the time of writing) to support AAR / Custom Views. You can find a link about this here:
https://developer.xamarin.com/releases/vs/xamarin.vs_4/xamarin.vs_4.2/#Android_Designer
It should be released to Stable shortly. For a non-beta/alpha workaround, I would highly recommend using this VS plugin for the time being which combines using Android Studio and Visual Studio to be the most productive when designing:
https://visualstudiogallery.msdn.microsoft.com/9f5a516a-f4d0-4228-9d25-d0273abebf33
For a more accurate timeline of these changes, you can view the latest blog article on the Beta channel:
https://releases.xamarin.com/beta-preview-1-cycle-8/
Upcoming Release Dates
Alpha – April 27th, 2016 (Evolve Conference)
Alpha 2 – July 13th, 2016
Alpha 3 – July 27th, 2016
Alpha 4 – Aug 2nd, 2016
Alpha 5– Aug 9th, 2016
Alpha 6 – August 12, 2016
Beta 1 – This Release!
Stable – Fall 2016
Thus if you wanted this functionality in your IDE, you will need to use XVS 4.2.X + in either the Alpha/Beta channels as of the time of writing.
Currently the Visual Studio Designer doesn't show Support Library elements.
You can use Xamarin Studio, which lately improved there Designer very much, and is easier to integrate with Visual Studio than Android Studio.
To download it go to http://download.xamarin.com/studio/Windows/XamarinStudio-6.0.2.73-0.msi (also available through your dashboard in www.xamarin.com under downloads, different versions).
EDIT: Currently you need to change the Cycle to beta (Help -> Check for Updates)
Related
I upgraded my build agent to Visual Studio 2015 Update 3 and I noticed that C# code analysis issues are no longer reported.
I am using SonarQube 5.6
Bogdan, the same happened to me.
You need to upgrade your C# plug-in to be at least version 5.3.1
Indeed, Visual Studio 2015 Update 3 introduced a breaking change in the Static Analysis Result Interchange Format (SARIF) generated by the C#/VB compiler. As a result the C# plug-in could not find any issue any longer. SonarSource reacted quickly by providing a bug fix version (5.3.1)
Note that this should not happen again as now SARIF has moved to version 1.0 (that happened in VS 2015 Update 3, and its versioning will be fully supported moving forward)
Our version of Microsoft Expression Blend Preview for Silverlight 5 has expired on 30th June and there are NO online license purchase options available.
The following link states that Blend is now an integral part of Visual Studio 2012, but with our current constrained development and release cycle we do not have the option to upgrade our entire enterprise class application to VS 2012. So, my questions are:
Can Blend (Preview for SL 5) licenses be purchased online? If yes, where?
If not, then how can we continue our Blend based development without upgrading to VS 2012?
Unfortunately, Microsoft left us down.
The only option is to go with Visual Studio 2012, as it includes Blend with it, but bear in mind, it is not smooth, buggy and crashes more than the Preview version for Silverlight 5.
I've even created a bug report on Microsoft connect, which was deleted strangely by microsoft.
PS : I tested the Update 1, Update 2 and Update 3, all of these on solution containing work done in silverlight 5 and telerik controls. It takes 15 minutes to open, and then crashes, this issues was not detected on Preview Version
For Now, We are changing the system date to a date before June 30, Open Blend Preview, and then fix again the system date (because if you don't, you will have nightmare with Skype and outlook :) )
I am trying to run an .ocx library for a VB6 project that I have. However, every time that it calls the first object property, it generates the error below:
Line 937: Property OleObjectBlob in ICImagingControl1 could not be set.
Line 937: Cannot load control ICImagingControl1; license not found.
Some forums mention that the cause is using an old VB6 version, or a missing file FM20ENU.DLL in System32 (my case SYSWOW64). I already upgraded too the latest VB6 version (which is still quite old) and made sure the file was in the right folder. Neither of them worked for me, any ideas why is this issue happening?
Thanks
I installed and uninstalled several times the software, which created a reference to the wrong ocx in the registry. To solve this, I uninstalled IC Imaging Control, proceeded to erase the references in the tree, and reinstalled the proper version.
I was asked by a client of mine to edit an old vb6 project and ran in the same problem.
Googled for a solution until I found this:
https://jeffpar.github.io/kbarchive/kb/195/Q195353/
Downloaded and executed the program and the project could be perfectly edited.
Original text of this Microsoft article:
Q195353: FILE: VBUSC.EXE Provides Licensing for Discontinued Controls
Article: Q195353
Product(s): Microsoft Visual Basic for Windows
Version(s): 6.0
Operating System(s):
Keyword(s): kbfile kbusage kbCtrl kbLicensing kbVBp kbVBp500 kbVBp600 kbGrpDSVB kbFAQ kbVBp600FAQ k
Last Modified: 21-JUN-2002
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows, version 6.0
- Microsoft Visual Basic Professional Edition for Windows, version 6.0
- Microsoft Visual Basic Enterprise Edition for Windows, version 6.0
-------------------------------------------------------------------------------
SUMMARY
=======
VBUSC.EXE is a file that installs the Design-Time Licenses for ActiveX controls
that shipped with earlier versions of Visual Basic, but are no longer supported
and have been discontinued with the current version.
MORE INFORMATION
================
The following file is available for download from the Microsoft Download
Center:
VBUSC.exe
(http://download.microsoft.com/download/VB60Pro/Install/2/Win98/En-US/VBUSC.exe)
Release Date: August 15, 2000
For additional information about how to download Microsoft Support files, click
the following article number to view the article in the Microsoft Knowledge
Base:
Q119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current
virus-detection software that was available on the date that the file was
posted. The file is stored on secure servers that prevent any unauthorized
changes to the file.
FileName Size
---------------------------------------------------------
VBUSC.EXE 88k
The following controls are no longer supported by Microsoft Visual Basic:
ActiveX Control Name Filename
------------------------------------------------
Desaware Animated Button Control ANIBTN32.OCX
Microhelp Gauge Control GAUGE32.OCX
Pinnacle-BPS Graph Control GRAPH32.EXE
Microsoft Grid Control GRID32.OCX
Microhelp Key State Control KEYSTA32.OCX
Microsoft Outline Control MSOUTL32.OCX
Outrider SpinButton Control SPIN32.OCX
Sheridan 3D Controls THREED32.OCX
The ActiveX controls listed above are no longer supported, but ship with the
Professional and Enterprise Editions of Microsoft Visual Basic for backward
compatibility when upgrading existing projects.
These controls do not ship with the Learning Edition of Microsoft Visual Basic.
For the Professional and Enterprise Editions, the controls are located on the
installation CDs at the following locations:
Microsoft Visual Basic Edition Location
----------------------------------------------------------------------
Professional 6.0 \Common\Tools\VB\Controls
Enterprise 6.0 \Common\Tools\VB\Controls
Visual Studio Professional 6.0 \Common\Tools\VB\Controls (CD2)
Visual Studio Enterprise 6.0 \Common\Tools\VB\Controls (CD3)
Each of these directories contain a README.TXT with instructions on how to
install the controls for design-time use.
NOTE: Using the Learning Edition to upgrade a project developed in an earlier
version of Microsoft Visual Basic might result in licensing problems for these
controls.
The VBUSC.EXE installs the design-time licenses for the controls listed above if
Visual Basic is detected on the computer.
REFERENCES
==========
For additional information, please see the following articles in the Microsoft
Knowledge Base:
Q194784 INFO: Controls Shipped in Visual Basic 6.0
Q172193 INFO: List of VB 4.0 Custom Controls Discontinued in VB 5.0
Does anyone know when stylecop will be released to integrate into VS2010. I know you can tweak the config files to integrate it at the moment, but it is not possible to view the UI.
A beta was released on January 04, 2010. It is easy to find via Google
You can find it here: http://stylecop.codeplex.com/ still beta but works
I didn't find out about this until I already upgraded VS2010, but according to Visual Studio Magazine :
In VS2010 Beta 2, many developers
reported issues when working with XAML
and Windows Presentation Foundation
and Silverlight. The VS2010 RC
supports Silverlight 3.0 apps.
Silverlight 4.0, still in beta, is not
supported in this release.
"We will be adding VS 2010 RC support
for SL4 with the next public
Silverlight 4 drop," explained
Guthrie. "If you are doing active
Silverlight 4 development today we
recommend staying with the VS10 Beta 2
build for now."
Being a developer, the paranoia set in....
Anyone know of any red flags or known issues to watch for?
Some of our developers have reported a high incidence of crashes working with Silverlight 4 in VS 2010 beta2.
One thing that helped was to view XAML in XAML mode not Design mode.
We also have seen issues using Blend in conjunction with VS 2010 beta2 as it can't handle solution folders.
FYI, the app crashes at least twice a day for me. Not all occurrences have been consistent. Those that were have been reported or previously identified. The main two that tends to crash it is switching between the XAML/Design view or attempting to deal with/switch back and forth between two instances of VS2010 open on the desktop at once.
Suggestion: Save and save often.