Bug 5134 - Error when creating a new GTK#2.0 solution
Summary: Error when creating a new GTK#2.0 solution
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: GTK# Designer ()
Version: 3.0.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2012-05-17 00:20 UTC by chinaguy_99
Modified: 2013-11-21 14:45 UTC (History)
5 users (show)

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


Attachments
error screen shot (62.68 KB, image/jpeg)
2012-05-17 00:20 UTC, chinaguy_99
Details


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:
Status:
RESOLVED FIXED

Description chinaguy_99 2012-05-17 00:20:11 UTC
I just installed a brand new Monodevelop, and first time to open, when i created a new solution for GTK#2.0, a error message prompted "Can't write into file Widget", and details as below, 

System.NullReferenceException: Object reference not set to an instance of an object.
   at MonoDevelop.Core.Assemblies.AssemblyContext.NormalizeAsmName(String name)
   at MonoDevelop.Core.Assemblies.AssemblyContext.GetAssemblyForVersion(String fullName, String packageName, TargetFramework fx)
   at MonoDevelop.Core.Assemblies.AssemblyContext.GetAssemblyNameForVersion(String fullName, String packageName, TargetFramework fx)
   at MonoDevelop.Core.Assemblies.ComposedAssemblyContext.GetAssemblyNameForVersion(String fullName, String packageName, TargetFramework fx)
   at MonoDevelop.Core.Assemblies.ComposedAssemblyContext.GetAssemblyNameForVersion(String fullName, TargetFramework fx)
   at MonoDevelop.GtkCore.ReferenceManager.Update(String assm_version)
   at MonoDevelop.GtkCore.GtkDesignInfo.UpdateGtkFolder()
   at MonoDevelop.GtkCore.GuiBuilder.GuiBuilderProject.Save(Boolean saveMdProject)
   at MonoDevelop.GtkCore.WidgetFileDescriptionTemplate.AddToProject(SolutionItem policyParent, Project project, String language, String directory, String name)
   at MonoDevelop.Ide.Templates.ProjectDescriptor.InitializeItem(SolutionItem policyParent, ProjectCreateInformation projectCreateInformation, String defaultLanguage, SolutionEntityItem item)
Comment 1 chinaguy_99 2012-05-17 00:20:58 UTC
Created attachment 1902 [details]
error screen shot
Comment 2 Marius Ungureanu 2013-11-21 02:59:18 UTC
Can't reproduce. Maybe this was fixed in the meantime?
Comment 3 Mikayla Hutchinson [MSFT] 2013-11-21 14:45:55 UTC
There have been a lot of changes in MonoDevelop.Core.Assemblies since then, I'd assume it's fixed unless we get a repro or a report against 4.2.x.