Bug 29973 - NullReference exception when using the Archive All publishing feature
Summary: NullReference exception when using the Archive All publishing feature
Status: RESOLVED DUPLICATE of bug 28615
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 5.9
Hardware: PC Windows
: Normal normal
Target Milestone: master
Assignee: Lluis Sanchez
Depends on:
Reported: 2015-05-12 10:38 UTC by John Miller [MSFT]
Modified: 2015-06-18 07:46 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 John Miller [MSFT] 2015-05-12 10:38:24 UTC

   When choosing the Build -> Archive All menu item, an NRE exception occurs. See attached logs for more info. 

**Steps to Reproduce:**

   Seems specific to users solution, I could not reproduce. It's unclear what would cause this. 

**Actual Results:**

   > ERROR [2015-05-09 13:44:36Z]: System.NullReferenceException: Object reference not set to an instance of an object.
   > at MonoDevelop.Projects.CustomCommand.ParseCommand(StringTagModel tagSource, String& cmd, String& args)
   > ....

**Expected Results:**

   No exceptions. 

**Build Date & Platform:**

   === Xamarin Studio ===

Version 5.9 (build 431)
Installation UUID: ec56b376-ac2f-4317-b40d-6c24618ef207
	Microsoft .NET 4.0.30319.34209
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

=== Xamarin.Android ===

Version: 5.1.0 (Business Edition)
Android SDK: C:\Programs\Android\sdk
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: C:\Program Files (x86)\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)

=== Xamarin Android Player ===

Not Installed

=== Build Information ===

Release ID: 509000431
Git revision: 7560726734fc7267de2fa9abed2509968deefaa8
Build date: 2015-04-17 17:09:09-04
Xamarin addins: 2e772c734ab3148054eae7bf8949f340fdeb5e5e

=== Operating System ===

Windows 6.2.9200.0 (64-bit)

**Additional Information:**
Comment 2 Greg Munn 2015-05-12 11:26:38 UTC
Something is trying to build a solution - do you have a solution open? Can you screencast this?
Comment 3 Greg Munn 2015-05-12 11:29:58 UTC
Sorry, I looked at the log before reading the description. I'll take look and see if I can find anything obvious.
Comment 6 Greg Munn 2015-06-01 12:35:34 UTC
Ok, 2 problems that I see.

1. There are merge conflicts in the IGS\package.config. Remove them so that the nugets will restore properly.

2. Building the portable project 'IGS' results in the NRE, archiving all yields this result because, each of the applications depend on IGS.

Examining IGC.csproj finds this bit of xml

        <Command type="Build" />

Basically an empty custom command section, removing it results in build of IGS.csproj and no more NREs.

I'll route this to the appropriate maintainer so that we can show a better error in this case.
Comment 7 Matt Ward 2015-06-18 07:46:40 UTC
Marking this as a duplicate of bug #28615 which has been fixed. Now when building the project with an invalid command you see the following error reported in the build output.

Build failed. Invalid custom command for 'Build' step: the path to the command to execute has not been provided.

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