I created an app for imaging application to start with.
Now I had to build another app which uses a lot of functionalities of the previous app.
I copied and pasted the first project, and changed the app Display Name, etc. in WMAppManifest.xml file.
But now when I try to deploy this app, I notice that the first app is replaced by this second one.
How can I resolve this? I suppose I require a different product/publisher ID for this app in Packing section. How do I obtain these?
You don't need to "obtain" these IDs. When you submit your app to the marketplace, they are automatically replaced by the appropriate values. When developing on your computer, just put whatever value you want. The values are located in the application manifest (WMAppManifest.xml).
You can create a GUID in Visual Studio by going in the "Tools" menu, then clicking on "Create GUID".
You need to change the product ID (it's a GUID you can generate a new one).
Related
In Google Play Console, I created a new app and uploaded an application bundle for internal testing.
Play Console set my app's application name to the applicationId field of my build.gradle file, which is not the application name I want it to have (lets say com.wrongName.app).
I want to change the application name, but if I upload a new application bundle, I get:
Your APK or Android App Bundle needs to have the package name com.wrongName.app
This thread seems to imply that I can still delete the app bundle and load a new one, since this is still a draft. But I see no way to delete an app bundle, or even delete my app.
Am I stuck with the wrong application name?
Yes you can delete the app bundle, and delete the app as well. There is a provision in the Play Console for that. The Package name has to be identical to your App Name as well, without which you will not be able to upload it.
I have two app service application and function apps [different solutions]. Both are developed using .Net core Visual Studio 2019.
I see different type of wizards for publish during publishing app service . This is creating confusion.
I would like to know, why there are different types of Wizards? Why in one solution its showing and other its not?
In general case, I can just click on publish and it will publish. However, in case of "pick a publish target" I need to download the publish profile and do "import profile". Will I need to take any extra care during "import profile" ? What are the difference between two types of publish? Which is the preferable way? Could anyone please help me understand this?
Any link/tutorial that will explain the step by step approach of "Pick a publish Profile" ? Thanks
Below screenshot shows, different wizard:
In the first image, you have already created a publish profile. Hence, it just straight asking you to publish.
In the second case, you don't have a publish profile yet so it is asking you to Import or create a publish profile. You can also create a publish profile by selecting App Service instead of IIS, FTP etc and then once the profile is created it will work like in your first case. And off course, import a profile which again should only happen once and thereafter it should automatically use that profile.
I am new to Azure WebJobs. For a mobile app we need some WebJobs that can run scheduled. My question is about the "Projects-Architecture" when it comes to WebJobs.
As far as i know, a new project is created for every WebJob. I am doing this by righclicking the main project -> add new azure webjob project.
But how are these projects "combined". There should be some reference to the parent project that i cannot find. I need to access the entities from the main project inside the WebJob. How should this be done?
Furthermore i am not sure wheter to implement Logic+Data access directly inside the WebJob or let the WebJob instead call another Controller to handle this?
Documentation on this is horrible, every help would be great.
They are not really "combined". There is a reference in the Web App (the webjobs-list.json) in properties that tells VS to publish the webjob when you publish the web app. If you need to access entity models in the webjob, then you need to add a reference to your other projects just like you would in any other project (add the project reference and then add a using statement in the webjob). The reference will get compiled into the webjob.
May I ask what are you trying to achieve via the web job? this would help in identifying why the need for accessing the models of your MVC app.
One suggestion would be to push the object from the MVC app to an azure queue and then access it via your job. Set it up in a way to identify new messages in a queue. (trigger). - not sure if this helps cause I am not sure how quick the web job is run and what are the other constraints you are working with.
When you add a new or existing WebJob Project to your solution, Visual Studio will take care of this for you. It is not something new, as if you are adding a console/windows service project to your web/MVC application.
If you need these projects to communicate, you till need to add references to your other projects just like you would in any other project which will in turn get compiled.
If you need to learn more and check some examples, this tutorial https://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-webjobs-sdk-get-started/ shows how to write code for a simple multi-tier ASP.NET MVC 5 application that uses the WebJobs SDK. Maybe that can give you some information on how to architect the application.
Feel free to recommend a better title or changes to my explanation below!
I am using Windows Azure Websites (for the first time) and have connected it to a solution in Visual Studio Online (also my first time). I was also able to connect to Visual Studio Online, create a project, throw up a master page and web form connected to a master page and my Azure website updated itself. Great!
My Issue
If I add another project to the solution it seems that this new project overwrites the files in the first one. I can't figure out how to set this up so:
Project 1 -> deploy to wwwroot (happens by default great!)
Project 2 -> deploy to wwwroot/sub/directory/ (doesn't seem to work)
Could somebody explain how to configure project 2 so that when the solution auto deploys to an Azure Website that it goes to a specific location?
Go to the Configure tab for the site in Azure portal.
Scroll all the way to the bottom then add a new application where ever you want like Project2 below.
Basically the 'Project2' part is the URL after the root '/' and the 'site\wwwroot\Project2' is where the actual folder should live under the site root
Download the publishing profile and import it in Visual Studio, then add the application name after your site name like below. Also remember to update the destination URL as well
hope that helps
Issue
A project based on custom VS2012 Windows Store app template wont show up when using the charms or contracts.
The steps I used:
Created a new project, Blank one.
Export a Project Template based on that and let it automatically install
Restart VS just in case
Create new Project based on template
Set it as a share target
Run the Project
Problem:
App wont show up as Share target etc.
The problem is not with the implementation of the contract