I am following a full stack web developer course on Udemy, building a webapp using Node and Express. After each section, I save a version of what I just completed, so I'll have a working version of the app to fall back on in case I screw something up in the next section. When I tried to use helmet I couldn't get it to work - it blocked everything (scripts, cdns, etc.). So I changed the code, eliminating the use of helmet. However, everything was still blocked. I went back to previous "helmetless" versions that worked before the introduction of helmet. But those are blocked, too! What could be causing this to happen?
Related
I am developing a Web assembly app with the template model which I had so far successfully migrated to .Net 6. It follws the template format of Client, Server, Shared. All working so far.
I wanted to move the ApplicationDBContext into the SHARED project as it feels a bit out of sorts in the SERVER Proj, and I need a another Webjob Project to reference it so it seemed like a good idea... (Checking in before I did it - just in case).
I moved it and changed the namespace and rebuilt the SHARED. Then thinking I would have a load of namespace fixups to do. Cutting a possibly long story short, the App then failed to build with ALL the packages in the client showing a yellow 'warning' triangle, but without indicating what the error/warning is:
I am also seeing this error:
Error NETSDK1082 There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. RaffleGames.Client
I decided to abandon the tidy up and revert to how it was... Sadly though, it is now broken with the same errors.
If I remove the reference to the SHARED project, then the warnings dissappear, but of course the CLIENT will no longer build.
Adding it back causes it to build but again with the above error.
I did wonder if some of the dependencies arent allowed in a blazor app as I did see that somewhere.. heres the project re-added:
I have re-started VS, and the machine, just in case... but to no avail.
I realise this is not a very clear question, but obviously something changed as a part of the build process and and I am looking for some pointers. Thanks in advance.
I have a published Google Slides Addon via the G Suite Marketplace SDK. After following the publishing guide everything looked great, until I wanted to bump the version number in the Google Cloud Console via my project's G Suite Market Place SDK Configuration tab.
I entered the number and hit "Save Changes", which put the new version life right away. However, it appears that a couple hours it will always be reset to the same old version (7 in my case). I bumped it again three times and have already tried to update the Chrome Webstore Draft, but it keeps being reset.
Checking the docs, I see no further steps required. I have also not found out yet when the reset occurs, it appears to be "over night" from a European timezone.
EDIT: what may also be relevant, the version in the Google Cloud Console does not automatically update when I publish to the Chrome Webstore. Instead, I manually put the newest version.
This issue should be fixed now.
Also the new publishing flow for GSM, which no longer requires to publish or do changes in the Chrome Web Store, is now live.
For almost every page I open in Firefox, I see this error in the Console of the developer tool bar:
(!) The Components object is deprecated. It will soon be removed.
The source is the html page. It happens with pages I create, but also on many common websites.
I found this documentation on Components object on MDN web docs, but that does not clarify a lot. Note that even that page shows this message(!)
It looks like a warning, but according to the Console filter, it is an error.
My main questions are:
Is this something for me, as a developer of the page reporting this, to solve?
If so, how do I go about that?
I am not aware of any problems as a result of this. For now, that is.
I have seen this for over a year, maybe longer. I mostly ignore this, but every now and then it starts nagging me again. I don't want my code to break suddenly and would like to get rid of this message obscuring other messages.
This is not for the developer of the page to solve.
While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case.
I restarted with disabled add-ons and the message was gone.
Then I enabled them one at a time and the culprit is
Selenium IDE.
A bug report on this issue was closed with Won't fix, with the message:
This error will resolve itself when we move to a native app later this year.
In a MozillaZine topic of 2012, it is explained how it could have been solved.
The first one is just a warning that the addon is using "Components"
directly, which won't necessarily always be possible when using the
Add-on SDK. (The preferred way to do it is to access the aliases for
Components.classes and Components.interfaces and such that the SDK
provides by requiring the "chrome" module.) It shouldn't be a problem
right now, but might become one in the future.
it happened for me after installing Selenium plugin in my FireFox.
After updating some NuGet packages, it turned out that some things in my website got broken by new code. I updated to the new Unity inversion control 5.0.0, etc. So after a while of hunting around and trying to fix it, I was able to get it to finally build and launch the site. However, the Unity IOC was broken because I kepts getting the "Error in Application '~/', controller must have a parameterless constructor". I saw that my couple of Unity files (UnityConfig.cs and UnityMvcActivator.cs) were gone, so I replaced them with ones I had in the backup folder.
Well, now it launches a loading site, but in VS it now says "UnityContainerExtensions.cs not found". I see that it looks all over for this file, around 'C:\ Program Files (x86)\Microsoft Visual Studio 14.0\VC...' and then it goes looking through 'c:\projects\unity]Abstractions\src\Utility...' - a folder that I can't even see.
This is in VS2015, doing a web application with Framework 4.6.
What can I do to just make it work again, as when I first had it so many months ago?
Alright, I was able to fix my Unity problem by rolling back on some of the packages. I'm the kind of person who likes to have no notifications, so I clicked Update All, and apparently the updates weren't necessarily compatible with my project here. To get it working again I has to bring back:
Unity.Abstractions = 2.0.0
Unity = 4.0.1
Unity.AspNet.WebApi = 4.0.1
Unity.Mvc = 4.0.1
Now to great relief, all works just as it did before!
However, I do wish I knew why the breakages happen and also why these packages are listed as updates when they are not going to work with my project.
Till the future, my system is going to have to consist of a Post-It "Do not update these xxxx packages, they will break stuff". And I wish to gain an understanding of what is the reason behind such Unity mess.
I am trying to get started in development of my website and plugins using Umbraco. When I download the binaries from Codeplex, the installation and running of the website works fine. When I downloaded the source code, All I get is a login screen even when the web.config files are the same. Am I doing something wrong or is there something I missed.
The path I use to map IIS to is
branches\4.1.0\umbraco\presentation
You need to compile the source code to get it to work.
To be honest, you shouldn't need the full source unless you really want to start hacking around in the core (which may cause you problems with future updates) or you want to see how stuff works. The Umbraco framework is pretty extensible, I've not found too much so far that I couldn't do without having to touch the core source.
I had a similar issue when running the source and that was that the hashing of the admin password did not work. So i debugged it to see what value was expected and then changed it in the database.