I have installed Visual Studio Code (ver 1.14) on Windows 7, and added the extension Azure Policy (ver. 0.0.22). After signing-in into Azure Cloud by using the Visual Studio Code Azure Account extension, I try to update the panel in the upper left side of the window in which the resources available in my subscription are listed, unfortunately an error message pops up which says:
command 'azureResource.refreshTree' not found
Does anyone has experienced same problem? Any idea about the root cause and how to solve it?
Thanks for any help
The problem was there for a few days till I rebooted Windows. I don't know if this was the real solution of the problem, but it worked for me.
Related
When trying to test my app on my device iPhone, I get the following error, I think it's something about registering my device.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3):
Error MSB6006: "codesign" exited with code 1. (MSB6006)
(multifacturacion.iOS)
The strange thing is that this same device in another mac with xamarin if it works and with the same project.
If someone can help me with this, I have several days looking for a solution.
This went away for me after I cleaned the solution in Visual Studio.
(yes this is a complete answer, there are no citations, this is just what I did to fix it).
Open the info.plist and check "Automatic Provisioning".
Thing is, I am having this error regularily. I am working with a local developer certificate created on my Mac using a free Apple Id, but without a paid Apple Developer Membership. I am using a Windows based devloper workstation and program in Visual Studio 2019 with Xamarin.Forms 4.0. To get local deployment working again, I need to visit the general settings on my iPhone and remove my trusted account from the list of developer apps under device management which basically not only removes the account but also the app from the device.
Then I need to remove all occurances of the corresponding certificate on my Mac within the Keychain Utility and even the mobileprovision file on my harddrive located somewhere beneath my user directory.
Now I have to Start XCode on my Mac, open the project, I am working on and have it automatically "repair" the signing certificate which basically creates a new one and registers it in the Keychain. The moment I run the app from XCode, I need to always allow keychain access and on my iPhone I can see the account appear in the general settings again which I have to manually trust... again.
THEN I can open the corresponding project in my Visual Studio on my Windows Developer Workstation, rebuild and deploy the app and get no errors.
Without being able to say why, it could happen even the next time I try to build and deploy the app, that this error happens again... this is very (!) inconvenient and I didn't find any real solution for it yet...
remove your certificates from keychains and add again, close Info.plist open and fill de information on bundle singing option, that works for me, remember link your device with you provisioning.
The answer of Mephisztoe worked for me, except that I am working on Windows and you find the scheme-property in the project-settings and not in the plist-file.
Furthermore be sure that you installed fastlane (just open Extras > Options > Xamarin > Apple-Accounts and click on "install fastlane") and added your Apple-ID there.
I also deleted the certificate with the keychain-utility. That's why I had to reenter my password on the mac as I clicked on build on my windows machine.
With these steps done I can finally work again...
If the certificate of Apple developer is expired, you can get the error like "codesign", so you need to create a new certificate in Apple Developer site (https://developer.apple.com/account/), then download & install to your computer.
I have been struggling with the same issue for several days, the error came only when I tried to publish the app from my Windows VS 2019. It had no further details of why it was behaving like this.
What I changed was:
Created New Publishing Profile & Certificates
Instead of selecting Release in Configuration as suggested in this Microsoft article, I selected AppStore from the configuration.
Tried to recreate the archive and it was completed successfully.
Now when I tried to publish it, I encountered few error messages, I fixed them and submitted the app again. It worked fine.
For me, the issue was that there was a popup asking for a password on the network-attached Mac. I had to VNC into it and enter the password.
For some reason the first time I did this (and chose "always allow"), it failed again with this error, but the second time I ran it succeeded.
You'll want to make sure to have an app-specific password ready if you haven't already generated one. I have no idea why, but it prompts you for one in VS.
I just downloaded and installed Visual studio on my computer (windows 8.1) to start building windows 8 apps. The problem is when I try to run any application this error message shows up (the application from this error message is called Parcels.comStarter):
Error 1 Error : DEP0700 : Registration of the app failed. Deployment
Register operation on Package
a783768f-d79c-495b-bf64-e59e4297fb42_1.0.0.0_neutral__1mfyfctfxa0tr
from:
(d:\Gebruikers\wardv_000\Downloads\Parcels.comStarter\Parcels.comStarter\Parcels.com\bin\Debug\AppX\AppxManifest.xml)
failed with error 0x8E5E0530. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) Parcels.com
I searched the entire internet but I didn't found a solution. I also did reinstall visual studio and I still have the problem.
Thanks in advance
Open the Services management console (services.msc) and stop the Windows Installer service.
In Windows Explorer, go to C:\ProgramData\Microsoft\Windows\AppRepository\ and rename PackageRepository.edb to PackageRepository.edb.backup.
Back in the management console, restart the Windows Installer service.
Now run Visual Studio as an administrator and open your project.
I was having this exact same problem, and the solution for me was to unlink my Windows account from my Microsoft account.
There are a couple of things to try.
Run WSReset (press [Win] then type wsreset)
Delete the metastore and remotemetastore folder here: C:\Users\%userprofile%\AppData\Local\Microsoft\Windows\SettingSync where %userprofile% is your username. (I suggest just renaming them to metastore.old and remotemetastore.old)
Make sure that there are no staged packages for the app in question.
If you re-deployed an app that was already installed by some other user, then you would get a deployment error. This should wear off if you change the identity in your package.appxmanifest fie.
You should try an OS refresh. You should not lose your apps and settings.
After that re-link your windows account to microsoft account.
If that doesnt work...The problem may be that visual studio is not able to delete the application data in local folder. So when you go in the location C:\Users\UserName\AppData\Local\Packages you will find application data of app installed in your computer, now you need to find your app's application data and delete the folder. The folder name is the same as the package family name which you can see in your solution.
now again open the solution and rebuild and your app will run. (hopefully)
close visual studio and simulator before deleting the folder.
make sure that your account is set as administrator.
I had the same problem with visual studio running under Parallels VM. The solution was to copy the project from a cloud based directory to a local directory.
It has been a while since I've published my app to Azure. During that time frame, I've upgraded my system from 32-bit to 64-bit meaning a fresh install of Windows and Visual Studio. And Visual Studio Update 3 came out and was applied. When I went to publish an update today, I received the following:
The following exception was thrown trying to publish: Root element is missing.
My web.config file looks fine so I don't think it's this issue.
The app works fine in debug mode so I don't think it's any of the .lsml files as is mentioned here.
And I tried this procedure to hand edit the .ls3proj file but it didn't seem to help.
I previously had an issue trying to publish when I upgraded from the standalone LightSwitch 2011 to Visual Studio 2012. I was able to overcome that issue using the method described in this thread.
Attempting to use this same method resulted in my new project has a full screen error saying "There are critical errors in the application definition metadata..." and 210 individual errors (max errors reached).
The first error, "Cannot create unknown type '{http://schemas.microsoft.com/LightSwitch/2010/xaml/model}GlobalAttributeGroup'." Doesn't make sense because that line in the .lsml is identical from the old project to the new project.
The second error, "Could not find any application definition in the project." Which I do not understand at all.
I am able to publish a simple "Hello, world" style app to my Azure account.
What could be causing this? How can I get more information about exactly which element is causing the issue? The log produced by running devenv /log was not helpful.
Matt Thalman was able to solve my problem over in the Microsoft Forums. The ServiceConfiguration.cscfg and ServiceDefinition.csdef were missing from the project when checked out of version control. Copying those over from a new project restored my ability to publish.
I'm happily in the middle of coding then I try to launch my app in debug mode but I get this error message.
Unable to activate Windows Store app
This app failed to launch because of an issue with its license
The app was launching fine a few minutes earlier so this came as a surprise. I tried restarting Visual Studio but doing so did not help.
I got the annoying "renew your developer license" dialog yesterday I think. It had renewed without issue.
How do I make this error message go away so i can debug my app?
Well, I got it working by deleting the main project's 'bin' and 'obj' folders. Cleaning and Rebuilding wasn't enough. Hope this answer saves someone else the few minutes of confusion I just experienced.
I recently had a similar issue. In my case I had to uninstall the re-install the app to get it working.
Hope this helps someone. Also, to find out further detail about why it failed, you can checkout the event logs:
Event Viewer > Applications and Services logs > Microsoft > Windows > Aps > Microsoft-Windows-TWinUI/Operational
There might be some more detail in there. In my case it was logged as an error event which said the app could not be launched because of a temporary issue with its license.
I just uninstalled the existing version of the app from the start screen, and then launched the app again from Visual Studio and it is launched just fine.
I think the reason behind this is because of renewing the license of Visual Studio and trying to launch an app that was installed when the previous license was active.
I see doing stuff with the bin and obj folders appears to be the accepted answer to this.
I fixed this issue by selecting the 'Uninstall and then re-install my package. All information about the application state is deleted.' check box under the Debug tab of the project properties. You can uncheck it once you've done it once for all future builds.
I haven't had any issue with this solution. Simple fix and you don't have to worry about someone doing something to folders that could cause bigger issues.
http://daxdude.blogspot.com/2013/04/c-error-unable-to-activate-windows.html
I've had this issue a few times now, most of the time deleting the Bin and Obj folders will clear the issue up (These folders are automatically generated during a project build so don't worry about deleting them)
I have found whilst debugging on a remote device (A tablet or phone) that Deleting these folders doesn't solve the problem though - in this case the best solution I have found is just to do a restart on the device I was remote debugging to.
Simple but it works!
I just cleaned my solution and re-started Visual Studio. That did the trick for me - and didn't involve hunting around for files to delete, so you might want to try that first.
go to BUILD-->Clean Solution and click and after its has been cleaned again go to BUILD-->Rebuild Solution. After it has successfully rebuilt your solution just deploy it(Ctrl+F5). This solved the problem for me.
I'm trying to log diagnostics into storage account.
Throw error
Nothing happens. No dialog box.
Any help will be greatly appreciated!
I would like to suggest you to check your csdef and cscfg files. If you can see any invalid configurations, they may cause issues in Visual Studio UI. In addition, everything we do in the Visual Studio UI can also be done by manually editing csdef/cscfg files. So if you can’t get this particular feature to work in Visual Studio, you can also manually modify the connection string. Please refer to http://msdn.microsoft.com/en-us/library/windowsazure/ee758697.aspx for more information.
Best Regards,
Ming Xu.
Sounds like there was a problem installing the Azure SDK. Have you used this before and it just started happening or is this the first time you tried to do this?
I would say uninstall/reinstall the SDK and Azure VS Tools.