compatibility

I have published apk to the Android Market, activated and setup for free for all countries. Android Market says, my application is not compatible with any of the devices. I can see an application when I access Android Market from the PC browser but I can not download it from any of the Android phone (the same device used to test application before release). How is that possible if I have just few requirements? I have tested the application on a few quite old devices before upload and it worked. Information from the Publishing options: This application is only available to devices with these

Assuming that vb6 does not run on Windows 8 because the VB6 run time libraries are not shipped with Windows 8, would it not be possible to install the VB6 run time library on Windows 8 and then then run VB6? Or is there another problem? Kris Erickson EDIT: Microsoft is going to support the VB6 runtime in Windows 8. VB6 apps still work in Windows 8 in the Developer Preview, as of September 13th, 2011). . They also run in the Consumer Preview and as stated above, Microsoft are committed to having VB6 just work in Windows 8. This is a very difficult question to truly answer, but I'll try and

I just used Android SDK Manager to update Android SDK Tools to revision 17, and Android Compatiblity to revision 7. Now, the program I've been running for ages crashes on startup. Narrowing down the issue, I have created a new blank project, added android-support-v4.jar to the build path, and changed Activity to FragmentActivity and that's all. Now it crashes. The error message is: java.lang.ClassNotFoundException: com.example.test.TestActivity in loader dalvik.system.PathClassLoader[/data/app/com.example.test-2.apk] The code is: package com.example.test; import android.os.Bundle; import

I have an installer that works perfectly under NT 5.x, Vista, and Windows 7. It contains the proper manifest for UAC on NT 6.x. But starting with Windows 7 RC, every time the setup program closes, Windows produces an erroneous "This program might not have installed correctly" message, even though the program did install correctly with no problems whatsoever. I never got these spurious messages in Vista or in Windows 7 beta. I sent a bug report to Microsoft, but have not heard back. I thought that this might just be a glitch in the Windows 7 RC, but the problem is still there on a fresh install

According to BOL (SQL Server Books Online) on sp_dbcmptlevel , This feature will be removed in a future version of Microsoft SQL Server. Do not use this feature in new development work, and modify applications that currently use this feature as soon as possible. Use ALTER DATABASE Compatibility Level instead. Now, the only TSQL way I know of checking database compatibility is through sp_dbcmptlevel . As far as I know, ALTER DATABASE Compatibility Level is just for setting the compatibility level, not getting info. How should one to get compatibility level without using GUI? Nick Kavadias

While only for two days now, I am definitely sold on using gradle for all of my Java projects, and drop pom.xml from the root of all my projects. However, I would like to remain maven-compatible, in the sense that I would like for a gradle task to be able to generate a suitable pom.xml at the root of the project should the user want it. At this moment, the only reference to a pom.xml I have is in this section of the build.gradle file (this is, with very few modifications, what is found here ): uploadArchives { repositories { mavenDeployer { beforeDeployment { MavenDeployment deployment ->

very straight forward question. My company has developed a windows phone 7 app and have been testing it on a windows phone 7 device. Can we safely assume that the same app will be backwards compatible and work seamlessly on a windows phone 8 device such as a Nokia Lumia 920? Thanks in advance! Yes it will work. But it won't take advantage of all the WP8 features like a real WP8 app would. I'd suggest that you create a copy of the project and update it to WP8 for a better performence. Also replace any listboxes with LongListSelectors for example. In most scenarios it should just work, but you