Storage of Web Application Deployment Settings in Visual Studio 2019 - deployment

I've had a crash of a Windows 10 development PC with Visual Studio 2019. I could restore everything but the deployment settings for a web application to an IIS webserver. I still have the old HDD with all user settings and alike. But I can't figure out, where these settings are stored. They seem not to be part of the Visual Studio project. Can anybody help me where (what folder, what file) these deployment settings/targets are stored?
I truly believe this issue hasn't been asked before, my apologies it if was. :-)

OK, hours of hours later, I found out the following and solved the issue:
The configuration is part of the project (C# in my case)
The profiles for publishing are stored under: [Solution]\[Project]\Properties\PublishProfiles\*.pubxml and *.pubxml.user
When you move your project to another folder or in case the folder name changes, you have to adopt the user config of your project: [Solution]\[Project]\{Project}.csproj.user There is a node:
<NameOfLastUsedPublishProfile>, which may contain (not always!) the
full path to the profile. This was the case for me. And since the
path changed, the profile was there, but simply not shown in the IDE.
Correcting this solved the issue for me. :-)

Related

Why is my Google Cloud Platform for Eclipse resulting in Error Not Found?

I upgraded Eclipse and moved to Google Cloud Platform for Eclipse for my existing Standard App Engine project. I also moved to Java 8.
Now, when I deploy my app, the size shown in the console is only 7.1mb vs. 220mb prior to the upgrade. And when I try to go to the app after deployment I get an Error: Not Found message.
Is there something in the setup for my new configuration that would be causing this?
Your question is indeed somewhat broad; you'll need to provide all necessary detail. A correspondingly general information page might help here, though, namely Eclipse "How-to Guides".
Have you adapted and re-written your app for Java 8? If so, in which way? Have you edited your app.yaml configuration file accordingly?
Cloud Tools for Eclipse writes out the app-to-be-deployed to a directory in your workspace called <workspace>/.metadata/.plugins/com.google.cloud.tools.eclipse.appengine.deploy/tmp/<timestamp>/staging-work/exploded-war, where <timestamp> is the time of the last two deploys. Look at the exploded-war directory and see what files are missing. You may then get a better sense of what needs to be remediated.

Service Fabric FabricRuntime.dll not found

I have tried to upgrade to the ne version of the Service Fabric preview code - 1.4.87-preview - and everything seems to have gone ok, but when I try to deploy a service I get an exception on run telling me that it cannot find FabricRuntime.dll. This goes both for my upgraded project, for newly created test projects and for all samples.
I can see that the DLL is present on the machine and that a system PATH has been set to the directory containing it.
There seems to be nothing wrong with my applications per se, as they deploy fine to a Party Cluster.
Anybody have any idea what is going on. Everything worked fine when I ran the old Service Fabric install. I have tried uninstalling service fabric and installing again, but it didn't help.
The answer is now posted on MSDN forums at https://social.msdn.microsoft.com/Forums/azure/en-US/6c8cc261-6c84-4097-be03-e8073cbc9397/unable-to-load-dll-fabricruntimedll?forum=AzureServiceFabric&prof=required
Copy of answer from MSDN Forum:
This is happening because FabricRuntime.dll is looking for zip.dll that ships with Service Fabric runtime. However since JRE is ahead in the PATH list and it also ships with a zip.dll, FabricRuntime tries to load zip.dll from the JRE folder and fails. We have fixed this issue by renaming our DLLs. The fix will be available in the next update of the SDK. In the meanwhile, you can fix this by adding "C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code" as the first entry in the system path and then restarting the machine.
This is the SDK issue, I've opened a GitHub issue at here

Publish-AzureServiceProject is not updating files on the cloud

I have a PHP Azure project which I have to manage with Powershell cmdlets. One of these, Publish-AzureServiceProject doesn't seem to be detecting file changes so these are not updated on the cloud (even though no errors are displayed).
I have remote desktop'd into the machines and the code is definitely not updated from weeks ago.
If I deploy to the local emulator, it is fine but this is much more obvious because it displays "removing old package" and "creating local package". The cloud package definitely contains the latest files, so the packaging is working fine.
Can anyone tell me how to force the publish to update the files on the cloud and more importantly, why this is not happening? Also, if I force the update, will it deploy to a new box and get a new IP Address?
Thanks.
It seems to work now.
I have removed and reinstalled azure libraries from my machine and created a new project from scratch and copied the original files over into it. I have not included diagnostics (not sure if that's an issue) and I have modified the Publish-AzureServiceProject script to select the subscription each time before it publishes.
It is possible that the subscription confusion was not helping (I have two Azure subscriptions and it might have used the wrong one at some point and done something weird) and also it was possible there was some conflict with various versions of the Azure SDK since I have been using it for over 6 months but at the moment, all is good.
A related article on my blog here: Problems with PHP Azure
Thanks for the interest

subversioning ipad app project

I am currently looking at setting up an Ipad app project into subversion.
Ive had a lot of experience with windows based development and .net. With this we have just created a repository in a network folder (by just right clicking -> TortiseSVN -> create repository) , than all we have done is our developers have checked out from this directory.
How do we go about doing this in xcode. I know subversion is integrated with xcode and I am pretty confident of doing everything (from tutorials) except for the creation of the repository.
Just wondering how we go about creating a repository in a folder based up on network folder?
Thanks in advance
Google for the svn book.
It should have everything you need to know with the exception of Xcode specifics.
Honestly, you probably don't want to create a repository on someone's development machine, especially if you are giving people network access.
You should setup an actual SVN server or use an online service.
Here is a question posted in 2009: SVN server for the Mac that's easy to set up?
Here is the "official" Ubuntu guide if you chose to run the SVN server on top of Ubuntu (which is my recommendation). Google for "install svn ubuntu".
Sorry I can't post multiple links yet.
Not 100% sure since I mainly use the terminal for svn operations on mac but
if you go in XCode to the scm you can configure the repositories for your project
once that is set up (I guess you know how to do this form your question), you simply you can go scm->repositories
select the one you want and you can then modify it

What are the effects of using VS2005 to migrate from .NET 1.1

I'm working on some legacy code for a client, involving Microsoft Content Management System (MCMS).
Currently, everything is local, the code, MCMS, SQLServer, and IIS (5.x).
I copied the project folder, and then opened the new copied solution in VS2005, and let it do it's conversion thing.
But now nothing works. I've nnotice there have been some changes to IIS profile. What are the extent of these changes...??
Also, my VS2003 fails to recognize the Web Project??
Anyone have any idea what's going on?
cheers!
Not really sure the extent to which MCMS affects anything (since I have not used that tool) but as to the question on the VS2003 not recognizing the web project, the issue is that when Visual Studio 2005 does it's upgrade, it changes the format of the VS2003 project files to VS2005 format. This means that once you have upgraded a project to VS2005 you can't go back and open it using VS 2003.
As far as changes to the web project go -
VS 2005 by default completely changes the layout and mode of your web projects. If you want to retain the familiar (and IMO better) web application layout from VS 2003 you need to use the web application project option which is available as a download - details are here
Hope this helps.