Hey guys my friend sent me his vb.net project made in VS2012 but I'm using VS2010. Now I can't open the file, it says 'This project is incompatible with current version of Visual Studio'. I have Googled it out and they said I need to change format version to v11 instead of 12 and also change target framework to 4.0. However, I am only able to change the format version to v11, but unable to change the target framework since I have nothing to access in the properties , as it shows 'there are no property pages for the selection'. How can I fix this?? Anyway to change the framework without going into properties??
Thanks!
Nevermind, I've figured it out guys.
open up the .vcxproj file using note pad and change the number from 4.5 to 4.0,so it should look like this
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
Related
I am learning Xamarin Forms for Visual Studio 2015 and trying to create a simple Shared project using Xaml but I keep getting InitializeComponent does not exist (as well as any reference to Xaml controls in cs classes).
It is my understanding that in the latest versions of Xamarin, Xaml works in Shared Xamarin Forms Projects (and not only in PCL projects). I've tried running the latest betas that got released less than a month ago but still no luck.
Any advice is greatly appreciated.
Turns out I had to manually change the properties for all Xaml files like so:
Build Action: Embedded resource
Custom Tool: MSBuild:UpdateDesignTimeXaml
For some reason adding new Xaml forms files doesn't set these by default in VS2015 with latest Xamarin.
I had the same issue. And it turned out to be that fully qualified Class Name (x:Class attribute in the main node) in the XAML file must match exactly the xaml.cs file's name. I corrected the namespace casing and it worked!!
This happens when your XAML markup is invalid. There is a background compilation task that parses the XAML file and generates a code file (this is normally hidden from the developer) which declares those control references. If your XAML is not valid then this task will fail silently, and your first hints are the symptoms you describe.
Comment out the contents of your XAML file using standard XML comment syntax (wrap it with <!-- and -->), then rebuild your project to clear out all of the errors. You may also need to comment out some code in your .cs files temporarily to get it to build. Once you get it building, then you can go back and start uncommenting your XAML until you find the part that was breaking it.
Try it:
Open the Package Manager Console, put the follow line:
update-package -project your_pcl_project_name -reinstall
Similar to this question, I'm having trouble with an old webforms project in vs2015. The code will compile and run without error.
If I enable a breakpoint and try to look at any value in a Quickwatch, I get the following error:
error BC32208: Project already has a reference to assembly
'projectname.resources'. A second reference to
'projectname.resources.dll' cannot be added.
Similarly, if I break into the code and hover the mouse over a variable name then I do not get a pop-up containing the variable's current value.
I also looked at this microsoft link to no avail.
Is there a workaround for webforms?
My project doesn't have any localized [culture-code].resx files.
There's no assembly tab in project properties.
Amber Zhang from Microsoft contacted me to inform me that this has been resolved in vs2015 update 2. Downloaded and verified today. Thanks Amber!
I have a VB.Net 2008 project that use ActiveReports. The problem is that any control on the report does not list the control's Name in the Properties window. All other properties seem to be there, just not the Name. The only way to change the name is to go into the forms .vb and change the name with a search and replace (like Me.Label1 to Me.lblAmount). All other forms are fine, it's just the ActiveReports forms. This happened just recently and there didn't seem to be any sort of update/event that triggered it. Anyone else have this issue before?
Thanks in advance,
-J
It is suggested that you download and upgrade to the most recent available build/service pack of the version of ActiveReports you are working with. And thereafter you should not face an issues.
The latest service packs can be downloaded from the following links :
AR3 : http://www.datadynamics.com/forums/121331/ShowPost.aspx
AR6 : http://www.datadynamics.com/forums/83/ShowForum.aspx
AR7 : http://our.componentone.com/groups/topic/activereports-7-service-pack-1-maintenance-release-now-available-2/
After the download, make sure that all of the dll’s of the upgraded version are present in the GAC. Also check that there isn't any dll of the previous version is present in GAC. After that remove all the ActiveReports references and then re-add the latest dll(s) in your project. Re-build the whole solution. You may also try creating a new project and check whether the name property appears.
Regards,
Mohita
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.
There is no editor available for 'file path here'. Make sure the application for file type (.vb) is installed.
This is the error that I get when I try to open a project I did a while back in VB. I tried a C# project and I can open the form for viewing fine, but for some reason VB won't work? Any ideas? I really don't want to do a repair on the whole application as it takes a while and I'm not even sure I have the ISO right now.
Check the compile mode of the object. If it is not set to "compile" then VS gets a bit weird about opening it up.