You need to tell Visual Studio that you deleted the files. Go to the project/solution folder where the files existed and remove them there. Visual Studio assumes that since you added the file originally, it should be published. It can’t assume that you don’t want it just because it isn’t in the filesystem. Think about … Read more
You can put your Google Play Developer Console into “Advanced Mode” by clicking the button in the top right corner. Then you can activate/deactivate APKs as necessary, and upload APKs specifically for beta testers only. You do not need to change the package name.
You can update the description and can change screenshot also and your app will remain same only the description and screen will be updated within two hours, and you don’t need to update apk. google will never ask to update the apk file when you change description or distribution. below is the screen shot where … Read more
EDIT: Google announced the web version of the Android Market earlier today. It appears that the “feature graphic” is used (in a smaller size) for the top features (see large images near the top: http://market.android.com/) and at the top of individual app pages. The little I found was this: Use a safe frame of 924×400 … Read more
if app is unpublished then is will not be available for download, will not appear in in-store search results, and simply cannot be installed from store. No details information from Google Play can be received even with direct URL to the application. Unpublishing however does not affect existing installations (so apps will not be automatically … Read more
For those using Visual Studio 2012 and the new publish configuration file (Properties/PublishProfiles/Local.pubxml) you can use this syntax in the file itself: <Project ToolsVersion=”4.0″ xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <PropertyGroup> <WebPublishMethod>FileSystem</WebPublishMethod> <SiteUrlToLaunchAfterPublish /> <publishUrl>$(MSBuildThisFileDirectory)..\..\obj\publish</publishUrl> <DeleteExistingFiles>True</DeleteExistingFiles> </PropertyGroup> </Project> Be aware that the $(MSBuildThisFileDirectory) property will resolve to the Local.pubxml directory. From there you should traverse up to get where you … Read more
There may be a few reasons behind the error which you can only identify by debugging. You can try to debug this error using the steps below: Navigate to the root directory of the application using CMD Run the application using the command dotnet run (yourApplicationName).dll If there are any errors, they should appear in … Read more
I had the same issue. Nightmare to identify the problem, because the logs and outputs show no errors or failures. I simply get “Build: 39 succeeded” and “Publish: 1 failed”. I resolved the problem by systematically removing all NuGet packages one at a time (and removing code that references it) until I identified the offending … Read more
You have to edit your .csproj file and in the Debug PropertyGroup you’ll have to add the following: <AutoParameterizationWebConfigConnectionStrings>False</AutoParameterizationWebConfigConnectionStrings> I have the following on Release and ReleaseCERT Configurations in my Project.csproj (I’ve only added the AutoParameterizationWebConfigConnectionStrings line): <PropertyGroup Condition=” ‘$(Configuration)|$(Platform)’ == ‘**Release**|AnyCPU’ “> <DebugType>pdbonly</DebugType> <Optimize>true</Optimize> <OutputPath>bin\</OutputPath> <DefineConstants>TRACE</DefineConstants> <ErrorReport>prompt</ErrorReport> <WarningLevel>4</WarningLevel> <!– add the following line to … Read more
If it is a web-site project, you may exclude certain folders and/or files as follows (see elements ExcludeFoldersFromDeployment and ExcludeFilesFromDeployment): <?xml version=”1.0″ encoding=”utf-8″?> <!– This file is used by the publish/package process of your Web project. You can customize the behavior of this process by editing this MSBuild file. In order to learn more about … Read more