Bug 5368 - when loading a new vb.net project it gives this error Error while trying to load the project '/home/mel/Documents/MyFirst/MyFirst/MyFirst.vbproj': Project does not support framework '.NETFramework,Version=v4.0'
Summary: when loading a new vb.net project it gives this error Error while trying to ...
Status: RESOLVED DUPLICATE of bug 6660
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: VB.Net Binding ()
Version: 2.8.6
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-28 09:38 UTC by Bill Hudson
Modified: 2012-11-16 16:58 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Bill Hudson 2012-05-28 09:38:13 UTC
It does however have this code window called Main.vb

Imports System
Imports Gtk

Public Class MainClass

	Public Shared Sub Main ()
		Application.Init ()
		Dim win as new MyWindow ()
		win.Show ()
		Application.Run ()
	End Sub
End Class
Comment 2 Matthias Fritzsche 2012-09-08 06:27:00 UTC
I confirm this bug.
I’m running debian wheezy amd64 and monodevelop
Comment 3 Jeffrey Stedfast 2012-11-16 16:58:28 UTC

*** This bug has been marked as a duplicate of bug 6660 ***