INCORRECT: 299

[GoogleCodeExporter]

What steps will reproduce the problem?
1. CLONE the current ArduPilot-Mega official repository to your own remote 
repository in code.google.com;
2. CLONE your new remote repository (the above clone of the official 
repository) locally to your development laptop; I used Smartgit;
3. LAUNCH Visual Studio (I own both VS2010Pro and VS2012Pro - it makes no 
difference); 
4. OPEN the ArduPilotMega.sln file (the primary solution for EVERYTHING, 
including the Mission Planner windows application);
5. BUILD the entire solution (a typical first step when any developer works 
with ANY new codebase which is supposed to be stable);
=> Build FAILS; currently missing an entire px4uploader.csproj directory; 
6. CLOSE The Solution and VS2010 (just a precaution); 
7. RETURN to Smartgit; 
8. CREATE & SWITCH to a new branch, call it (say) "FirstBuildAttempts";
9. (re)LAUNCH VS2010 and re-open the ArduPilotMega.sln file; 
10. DELETE the entire (missing) project reference for the px4uploader project, 
JUST to try & get SOMETHING to compile; 
11. ATTEMPT to BUILD The Solution;
=> Build FAILS; this time with 299 errors and 50+ warnings, the first of which 
is "Error 1 The type or namespace name 'Reactive' does not exist in the 
namespace 'System' (are you missing an assembly reference?) 
C:\Projects\pcl\Tools\ArdupilotMegaPlanner\Mavlink\MAVLink.cs 3 14 
ArdupilotMega"

What is the expected output? 
A completely & successfully built solution, with working MssionPlanner 
application; 

What do you see instead?
299 errors message from what is typically supposed to be bulletproof or at 
least COMPILABLE code. Every day. No exceptions. 

What version of the product are you using? On what operating system?
ArduPilot-Mega v1.2.20 (it appears)

Please provide any additional information below.
I am committed to helping with bug fixes and enhancements (my twin brother & I 
have compiled a list of enhancements) to the Mission Planner software, but the 
entire codebase has GOT to be reliable on a daily basis... that's how 
successful opensource projects STAY successful. 

Original issue reported on code.google.com by markevogt on 18 Nov 2012 at 6:33

[GoogleCodeExporter]

DOES anyone know how I can EDIT the subject of my defect? 
I inadvertently hit the submit button before looking it all over :-( ...

Original comment by markevogt on 18 Nov 2012 at 6:57

[GoogleCodeExporter]

You need to set the correct reference path in the project settings. Since this 
is an absolute path, your path may not be the same as the path of the developer 
here. This will eliminate most of these errors but there are 2 missing 
references anyway and these are the assemblies "system.reactive" and 
"transition". Besides that it complains about a missing certificate file for 
manifest signing.

I still can´t believe that this really happens.

Original comment by ka...@gmx.de on 19 Nov 2012 at 7:06

[GoogleCodeExporter]

Thanks for the tip! Turns out I googled /found this same answer in a
May2012 thread after I posted; I added the reference path c:\program fields
(x86)\APM Planner,  and *poof* - 299 vs2012 errors disappeared in an
instant.  But building still generated 2 more new errors -  vs2012 couldn't
find dpinstx64.exe and dpinstx64.exe where The Solution expected.  Adding
another reference path "c:\program files \APM Planner \drivers" did NOT
work -  I really needed to override where The Project went to get these
files,  so I actually re-added them to the project,  using the location
(above) where they really exist on my machine.  That WORKED, and now leaves
1 error message I haven't sorted out : a reference to version.exe file
"exited with code 9009"...is the only clue I have..... got any ideas?

Original comment by markevogt on 19 Nov 2012 at 7:49

[GoogleCodeExporter]

Sorry, get the same SH*T Error and i´am quite sure that the repository is 
messed up totally. These files did not exist also. There is only a file 
dpinst.xml in /Drivers and that´s it. It is referenced in program.cs

Original comment by ka...@gmx.de on 20 Nov 2012 at 9:51

[GoogleCodeExporter]

UPDATE - and RESOLVED: 
I researched the "code 9009", and it turned out the command was INVALID because 
there was NO version.exe file in the \bin\debug directory !

Per what appears to be a conscious decision to expect new APM Planner 
developers to actually install the APM Planner in their DEV environment in 
order to leverage the files included with the installer (and therefore NOT have 
to include them in any code repositories), I manually copied the version.exe 
file from the \APM Planner\ install folder, and into The Solution's \bin\debug 
directory...
=> The Solution now builds SUCCESSFULLY. 
:-)
-MV

Original comment by markevogt on 21 Nov 2012 at 3:17

[GoogleCodeExporter]

Ka,
I finally got the @#$%^& codebase to compile, and have been making several
(hopefully useful) enhancements to the APM Planner application itself, and
pushed those changes to my repository.
See my responses in the various forums for steps needed to get the current
codebase to compile.
Let me know if you wish any assist from me.
:-)
Cheers,
-MV

ps - even after compiling successfully, "enhancing" the APM Planner really
amounts to wading through a lot of poorly-documented, weirdly-architected
code, making changes, building, then MANUALLY copying the updated
ArdupilotMegaPlanner10.exe  file from my source code repository to my APM
Planner install directory. As far as I can tell, the .MSI file originally
used to install all of the ArduPilot-Mega applications on your laptop is
NOT a part of the overall solution file - to me that sucks, and I don't
understand why The Creators are doing things this way - it only makes
people come visit, give things a try, then run screaming off into the
night...
:-|
...but I'm committed to becoming a contributing member of this project,so
I'm going to persevere.
:)

Original comment by markevogt on 24 Nov 2012 at 11:17

[GoogleCodeExporter]

Original comment by Meee...@gmail.com on 27 Nov 2012 at 10:31

• Changed state: WontFix