I have a couple of extensions installed on my Azure DevOps Server 2019 Update 1 patch 7.
The thing is, that all of them keeps failing on an regular basis.
But I have no idea where to look for trouble shooting...
I've tried reinstalling some, but they still doesn't work.
Then, a while later. They are ok again :/
I thought installing patch 7 would help, but the issue came back shortly after...
Related
I have a blazor webassembly app that is working fine and it is split in webassembly talking to a web api version all .Net Code
I use VS community Edition 2019 and suddenly after many modifications to my code I noticed that I am not able to debug and see any variable content(unable to Evaluate) at any break points anywhere in my web assembly app. I tried with an old version of my code which I know it was working then and same issue, so it is not the code.
I tried upgrading VS to 16.11.75.64347 ( from 16.6 something) without success and even uninstall & reinstall VS with no success.
The only new thing on my station was a windows update this week.
Is someone had something similar happening this week?
ps: What is weird is that I do not not have this problem in my web API solution portion just the webassembly solution.
I think I've been badluck to find many not working thread but finally it was simply to close VS . delete the .vs directory tehn relod the solution and it was OK. It is weird though that many old version of my code that never had this issue had the same problem. It was impossible to have all those .vs not working although I had not touched them in weeks. Anyway it is now working.
I have an Azure MVC project, and when I try to debug it, it hangs at "Starting the role for the application in the Microsoft Azure compute emulator..."
After a while, if I try to hit the debug button again, it gives the error "The debugger cannot continue running the process. Unable to start debugging."
Any idea what the problem could be? The Azure storage emulator is running when this happens.
There are various things that can cause this and they are not all easy to find! It can be caused by a mismatch between the version of Azure tools referenced in the project and that installed on your PC.
I have had to remove everything related to Azure once and reinstall from scratch!
Another potential problem is if your WebRole.OnStart method keeps erroring, in which case, Azure will attempt to continually restart it and that can carry on for a long time. If this happens, it should eventually tell you that the roles are taking too long to start.
There can be problems if you are trying to use IIS instead of IIS Express, I have never got full IIS to work with the Azure debugger.
Try building a simple Azure app that references a default MVC app as a way to make sure it is not caused by mistakes you have made in your code or configuration. Good luck!
Not sure if this is your exact issue or not but I found the following which fixed my problem: https://stackoverflow.com/a/35407737/1399978. Issue is due to a specific Windows security update (KB3126593). Uninstall the update an everything works as it should. Hope it helps.
I know this might not help a lot of people who have been having similar problems, but I just want to note here that my issues went away when I upgraded to Visual Studio 2015 and Azure 2.8. Thanks for all the input, everybody!
I'm in the process of diagnosing this issue and I will update as I learn more but I wanted to post what I have in case there's a quick fix/someone's seen this already.
I have a MVC5 project, .NET 4.5.2, Visual Studio 2015. I recently started using C# 6 so in order to get Razor to work I had to install the CodeDOM compiler Nuget package. Everything works on my local machine (of course it does).
My current stable Azure site is on a Git commit that is NOT using C# 6, but is using .NET 4.5.2 and VS 2015. So the only big difference between my latest commit and the stable commit is the introduction of C# 6 and Roslyn.
When I deploy the new commit to Azure, I consistently get 502 Gateway errors after it spins for up to 2 minutes. On a MVC action that does NOT return a view but a Content action result, it will eventually return content although it's pretty slow. When I go to Kudu and view processes, I can see the Roslyn compiler runs and I was noticing last night that the w3wp process would restart every so often, usually after I get the 502 on requests.
If I redeploy my earlier commit, it works fine.
My next steps really are to isolate the issue to a blank web app using C# 6 and MVC 5, to see if that is the root cause--but my educated guess is the introduction of the Roslyn compiler is messing things up in Azure.
Anyone have any ideas? I'll update this as I learn more, but I have a busy day and weekend ahead.
Figured it out, slowly but surely, took me all day. I deployed each commit since the last stable one and found the commit that introduced the issue. In the commit I had introduced some more TypeScript files. Turns out these were NOT compiling in Kudu/Azure and so the JS files were missing, causing my bundling/minification framework (Cassette) to try to resolve references--which it never resolved and caused a StackOverflow or loop issue (separate bug) which caused my w3wp process to crash. This is why it was almost impossible to debug and also why my non-Razor actions returned--they weren't rendering the bundles so it didn't call into Cassette.
I included the generated JS files in the project and that fixed the problem. I think I will just edit my Kudu deployment script and call tsc manually on my tsconfig.json file so it compiles on build properly.
I had a Visual Studio 2012 project that I imported into Visual Studio 2013. I upgraded Entity Framework to version 6. I got the following error when I started the first time: Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'. Since this was a prototype app, I wasn't concerned about Glimpse, so I uninstalled it via NuGet, which removed the error and I carried on.
Now, I'm deploying to Azure websites and I keep getting that error!
Glimpse is uninstalled.
It works fine in release and debug locally.
I tried putting System.Data.Metadata.Edm.MetadataWorkspace.ClearCache(); in the Application_Start like this says. (Even though I don't run queries in Application_Start
I suspect I have a caching problem on Azure, but I'm not sure. How do I get the Azure deployment to remove Glimpse like the local install has?
Update: "Fixed"it by deleting the azure website and recreating it. Would still love to hear how to do with this without going with the nuclear option.
This is a bug and is fixed in the release that will hopefully be going out tomorrow - see here for more details https://github.com/Glimpse/Glimpse/issues/540.
I also faced this error and later on found the resolution.
Issue was that I had MVC5 and EF6 based solution and i had imported Glimpse.mvc4 and Glimpse.ef5 packages and they were incompatible i think .
Once i upgraded to Glimpse.EF6 and Glimpse.MVC5 it started working fine.
also had the same one, when I opted to remove Glimpse.
you can prevent this by deleting the bin/ and obj/ folders from your project folder(s) as Glimpse is copied to your bin during debugging.
I have gone here on CodePlex and downloaded nopCommerce v2.60. I am on a Windows 8 Pro 64x Machine, I have .NET Framework and SQLEXPRESS 2012 installed.
The nopCommerce solution installs perfectly fine, no problem ! All front-end stuff work fine. But when I try and access:
localhost:xxxx/admin
I get the following error:
I have already tried re-installing with fresh database and files, but no success. I don't know how to get it to work. Before this use to work no problems at all!
You need to BUILD the whole solution before running. :)
Ok after an exchange of emails with a friend of mine who is really good at C# and has excellent experience with nopCommerce. He too was able to duplicate the problem on his machine running Win 8 Pro 64x along with VS 2012, like me.
It turned out, for some strange reason, one must build, and re-build the solution a couple of times before running it in VS 2012.
So open up your nopCommerce fresh in VS2012, and before you run it, re-build the solution 2 or 3 times, and then run it.
That was the fix for me. So annoying that I spent so much time stuck with it, but I'm glad it works now.