Wally,

I think I was wrong about what I thought I observed, although that doesn't 
diminish the finicky-ness of adb.  :)

I don't know whether this is a Visual Studio bug or not, but it turns out that 
the problem was being caused by having two projects with the same name in 
different solution folders within the same solution.  I am using a hierarchy 
like this for my solution folder structure:


·         MD [Mono for Android projects under here]

o   CrossPlatform

§  MyLibrary [shared code files across all - file links]

o   MyApp [this has platform specific code/views, etc.]

·         MT [MonoTouch projects under here]

o   CrossPlatform

§  MyLibrary

o   MyApp

·         WM [Windows Mobile projects under here]

o   CrossPlatform

§  MyLibrary

o   MyApp

·         WP [Windows Phone projects under here]

o   CrossPlatform

§  MyLibrary

o   MyApp

With this configuration, MD\MyApp does not show as deployable, but if I change 
the name to anything else, it shows up as deployable.  My guess is that it is 
using the first "MyApp" project it finds for the deploy properties or failing 
because it found more than one.

For now, I am just changing the names of my application projects to be unique.  
In the future, it might be good to have the option to do the above.

Thank you,

Chris Tossing
Software Engineer
G4S Technology Software Solutions LLC
Direct Dial:      +1 (781) 457-0779
Cell:                +1 (847) 942-0359
[email protected]<mailto:[email protected]>
www.1f.com<http://www.1f.com/>
21 North Avenue, Burlington, Massachusetts 01803 USA

P Please consider the environment before printing this email

From: [email protected] 
[mailto:[email protected]] On Behalf Of Wally McClure
Sent: Monday, January 16, 2012 10:16 PM
To: [email protected]
Subject: Re: [mono-android] VS not recognizing manifest for my application 
after code restructuring

Chris,

Thanks.  This is really good information.  it just reinforces to me the 
finicky-ness of adb.

Wally
________________________________
From: [email protected]
To: [email protected]; [email protected]
Date: Tue, 17 Jan 2012 02:57:01 +0000
CC: [email protected]; [email protected]; 
[email protected]
Subject: Re: [mono-android] VS not recognizing manifest for my application 
after code restructuring
I'm not sure what was going on, but I believe that what fixed the problem was 
killing adb.exe.

I found that I was able deploy if I opened the project file for the android 
application directly instead of opening the solution file, which made me think 
it might be something wrong with the solution file, but I didn't see anything 
there that would cause this.  I ended up noticing that I had file locks by some 
process and found that it was adb.  Killing it and reopening the solution made 
it deployable again.  It appears that this was some kind of caching issue?

Oh, well.  It's working now.

Thank you,

Chris Tossing
Software Engineer
G4S Technology Software Solutions LLC
Direct Dial:      +1 (781) 457-0779
Cell:                +1 (847) 942-0359
[email protected]<mailto:[email protected]>
www.1f.com<http://www.1f.com/>
21 North Avenue, Burlington, Massachusetts 01803 USA

P Please consider the environment before printing this email

From: Tossing, Chris
Sent: Monday, January 16, 2012 9:32 PM
To: Discussions related to Mono for Android
Cc: Tossing, Chris
Subject: VS not recognizing manifest for my application after code restructuring

I just did a significant restructuring of our codebase, and Visual Studio is 
now not recognizing our android application project as a deployable project.  
It is also not recognizing the AndroidManifest.xml file when I go to the 
project property pages, and when I click the "Click to add one" link, it 
crashes Visual Studio.

I checked the project file, and it is still marked as 
<AndroidApplication>true</AndroidApplication>.

I did a compare with the previous version, and the only thing I changed in the 
project file that I'm seeing might be related is that I modified the 
RootNamespace and AssemblyName.  I tried modifying the AndroidManifest.xml file 
to set the PackageName to the same value as the AssemblyName (they were in sync 
prior to my restructuring) just in case that was the problem, but it didn't 
appear to have any effect.

How does Visual Studio determine if a project is deployable?  (I know it has to 
have the AndroidApplication set to true, but there is obviously something else 
preventing deploy at present)

Thank you for your help.

Chris Tossing
Software Engineer
G4S Technology Software Solutions LLC
Direct Dial:      +1 (781) 457-0779
Cell:                +1 (847) 942-0359
[email protected]<mailto:[email protected]>
www.1f.com<http://www.1f.com/>
21 North Avenue, Burlington, Massachusetts 01803 USA

P Please consider the environment before printing this email


________________________________
The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International 
Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal 
and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, 
forwarding, copying or use of this communication or the information in it is 
strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender 
and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek 
appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.

_______________________________________________ Monodroid mailing list 
[email protected] UNSUBSCRIBE INFORMATION: 
http://lists.ximian.com/mailman/listinfo/monodroid

________________________________
The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International 
Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal 
and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, 
forwarding, copying or use of this communication or the information in it is 
strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender 
and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek 
appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.
_______________________________________________
Monodroid mailing list
[email protected]

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid

Reply via email to