publishing

I have a project I made in Visual Basic 2008 Express. I converted it from someone else's C# project, but it works. It has several DLL dependencies. I went to publish my project so I can install it on another machine and for each DLL, I get an error: "Assembly must be strong signed in order to be marked as a prerequisite." I've done some research, but am not finding a lot and what I have found I don't really understand. What does this error mean? What is the best way to resolve it? One other thing: it took me a LONG time to be able to get all my dll's to reference correctly, so I prefer that

I have tested this app on the Android emulators, phones, tablets, and Google TV. Its works. When I published it Google Play, the app is not visible. Below is the manifest. I sincerely appreciate any insight as to the problem. Thank- you. <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.zzzz.xyzxyz" android:installLocation="internalOnly" android:versionCode="4" android:versionName="1.4" > <uses-sdk android:minSdkVersion="8" android:targetSdkVersion="15" /> <uses-feature android:name="android.hardware.touchscreen" android

Background The Android developer console has 3 tabs for publishing the app's apk file: alpha, beta and production, as shown here: as I recall from one of Google IO lectures, one cool way to check how good is your app before making a 100% scale publishing, is to allow only a percentage of the users to download the app first. I think it's called "staged rollouts" , because you can rollout the publishing in case it had too many problems to be published to all. My question What is exactly the difference between them, especially between Alpha and Beta? Only the production stage is available for

I am currently attempting to use Visual Studio 2010 'Publish' and MSDeploy functionality to handle my web deployment needs but have run into a roadblock with regards to customizing the package depending on my build configuration. I develop in a 32bit environment but need to create a release package for a 64bit environment, so in the 'Release' configuration I have a post build event that copies the 64bit version of a third-party dll into the bin directory overwriting the 32bit version. When I use the 'Publish' functionality, even though the correct 64bit dll is being copied to the bin directory

I'm just about ready to publish my first app to the Android market, and I'd like to know if any of you have any tips about any experiences you may have encountered in regard to publishing an app that goes beyond the obvious and already documented. Any hidden caveats and/or ideas about what to do before publishing an app to the market? For instance, a buddy of mine recommended that I remove any and all comments in my code just in case someone gets to the source code, thus making it more difficult for the would-be "code jacker" to decipher the code. I thought that was a sensible suggestion. What