aspnetcoremoduleV2 missing from iis modules after running the runtime bundle - asp.net-core

I dont have aspnetcoremoduleV2 in iis modules, even after installing the runtime/hosting bundle
so I cant deploy or test any core service
P.S: I used to have the moduleV2 in iis, but I accidentally deleted some files from C:/inetpub folder (not 100% sure if any files were actually deleted), but since then the module disappeared and all core apps are giving me
"aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list using IIS"
in folder Systerm32/inetsrv the module is missing, when I tried to add it manually and and it in the app.hosting file the iis (sort of crashed) no app was able to run until I removed these Manuel edits
I tried to re-install iis several time/ reinstall the bundle but had to luck

following from #brandoZhang's answer & iis docs here
I have done the following and its now working
1- delete the current aspNetCoreModule (I guess this part was unnecessary)
2- install the module manually if it doesnt appear in iis modules after downloading the runtimebundle
open cmd as admin
navigate to inetSrv location "C:\Windows\System32\inetsrv"
run: appcmd.exe install module /name:AspNetCoreModule /image:%windir%\system32\inetsrv\aspnetcore.dll
ans same for aspnetcoremoduleV2, but its location is in different place
mine was in %Program Files%\IIS\Asp.Net Core Module\V2\aspnetcorev2.dll
if a duplication error appeared, delete the old one and then re install it

Related

setup npmrc _auth for 2 registries

I have a set of js libraries, lets call them myLib, it is in form of workspaces so I have myLib-common, myLib-hello, myLib-world and so on. In the root of the myLib, I have .npmrc file to set npm registry and authentication.
I have 2 npm registries in nexus:
https://nexus/repository/project-javascript
https://nexus/repository/project-javascript-dev-repo
the first one is proxy registry that uses some other internal packages and then npmjs registry in order to be able to install dependencies. The second one is to publish new versions of the myLib packages for others to use.
Both of those registries requires authentication (for now, it can be the same user). When I add _auth into my .npmrc file, it works fine both for installing depndencies and also for publishing new versions into second repository. But I get warnings from npm that this is not ok. I've tried to "scope" the _auth token but it works just for the first registry and it wont let me publish packages due to authentication.
I have tried various versions like
registry=https://nexus/repository/project-javascript
//nexus/repository/project-javascript/:_auth=<base64>
//nexus/repository/project-javascript-dev-repo/:_auth=<base64>
and also
registry=https://nexus/repository/project-javascript
//nexus/repository/project-javascript/:username=user
//nexus/repository/project-javascript/:_password=<base64>
//nexus/repository/project-javascript-dev-repo/:username=user
//nexus/repository/project-javascript-dev-repo/:_password=<base64>
even extra quotes around tokens and so on but I'm still hitting not authenticated when publishing. When I remove everything and have just
registry=https://nexus/repository/project-javascript
_auth=<base64>
it works just fine for both installation and publish.
One more thing. I kinda need to have the auths in git and I'm still kinda unaware of how _authToken works (I believe it is setup locally, so everybody who works with the project would need to run their own npm login resulting in different authToken).
I've ran out of possible options here (the ones I was able to find through google). Is there a way I can set it up properly? Or way to easily debug the process of publishing so I can see where/how the token is loaded?

DNN 7 issue with SupportedModules attribute

I'm an experienced (ASP.NET|Java|PHP|web) developer, new to DotNetNuke.
Currently I'm following a blog tutorial to try to get an Angular module up-and-running in my local installation of DNN 7 (http://www.bitboxx.net/Blog/Post/505/DNN-module-development-with-AngularJS-Part-1#)
My environment: Windows 2012 Server R2, SQL Server 2016 Express, Visual Studio 2015 and DNN 7 on IIS 8.
DNN nuke runs fine.
I installed the downloaded module from the blog to my DNN. I'm having problems to run the HelloWorld example (at the bottom of the 2nd part of the course).
Through some trial-and-error I found out this has to do with the [SupportedModules] attribute on the controller.
Without this attribute it runs fine, but with the attribute it won't.
How does DNN determine the name of the module? The "installation" process was no more then unzipping the modules contents to the DesktopModules directory within my DNN directory (in inetput\wwwroot).
Do I need to install/configure the modules in Settings > Extensions?
Or am I missing some other point with regards to the DNN 7's security?
Thanks in advance for any help/thoughts!
Yes, you need to install the module through the Extensions mechanism in DNN. This will register the module so DNN is aware of the module as well as make sure the files get copied to the right places, in accordance with the installation manifest (the .dnn file you should find inside that .zip file)
However, looking at the blog article you referenced, I don't see an actual installation zip file anywhere. The only download I found was for the project as a whole. You would need to package your compiled solution into an installable zip file (with a .dnn manifest file) or you need to manually register your extension from the Extensions page.
On that page you should click the "Create New Extension" button which will walk you through supplying details for the module. Choose Module as the Extension Type
Only a few of the items are required. The "Name" you use for the module will be the name you use in SupportedModules. It will also default your folder name (the folder in /DesktopModules) to the module name. Friendly Name, incidentally, is what will be displayed in menus and such.
Once you've created the module it should be registered with DNN. You will probably need to restart your AppPool and website for the change to take effect.
FYI, SupportedModules isn't strictly required. If you're building this for a client and not building this for distribution.
Hope this helps.

Modules not loading in platform

Despite a successful build, no modules will load. The Browse menu is empty (except for Assets) and custom modules in the Configuration menu are missing.
After downloading the most recent build from our repository, I followed all steps in the "Source Code Getting Started" page. It has been a few months since looking at the VC documentation, and it looks like it has been updated. I recall an extra step after creating the Assets virtual folder in IIS that isn't there now. Is there perhaps a step here that is missing since the docs update?
Fwiw, the build deployed in our QA environment is fine. This is the same code, but I am trying to run locally and am having no luck with modules.
Virtual folder for Modules is optional in IIS and this step was skipped in the updated docs. But adjusting permissions in needed: "Open properties for vc-platform\VirtoCommerce.Platform.Web\Modules (create this folder if not exsist) folder and give permission Modify to IIS_IUSRS user group as shown above."

can I install wamp twice in different folders?

I'm facing a problem due to the folder name "Program Files" in which my wamp is installed.
I'm using Yii Framework to create a web app.
While running a command
yiic webapp c:\Program Files\wamp\www\YiiApp
it gives error due to the white space in the folder name.
The error is as below:
C:\Program Files\wamp\www\yii-1.1.13.e9e4a0\framework>yiic webapp c:\Program Fil
es\wamp\www\YiiApp
Error: Unsupported VCS specified. Currently only git and hg supported.
USAGE
yiic webapp <app-path> [<vcs>]
DESCRIPTION
This command generates an Yii Web Application at the specified location.
PARAMETERS
* app-path: required, the directory where the new application will be created.
If the directory does not exist, it will be created. After the application
is created, please make sure the directory can be accessed by Web users.
* vcs: optional, version control system you're going to use in the new project.
Application generator will create all needed files to the specified VCS
(such as .gitignore, .gitkeep, etc.). Possible values: git, hg. Do not
use this argument if you're going to create VCS files yourself.
What should I do? Please suggest me something.
The second install will have superceeded the first. In other words Wampmanager and Apache and MySQL will be being started out of the new folder.
As per your question on wamp forum, copy wwww/subfolders into the new location and then copy ONLY YOUR databases from mysqlx.y.z/data into the same place in the new location.
Then delete the folders from program files.
You only need one wamp ( Apache/MySQL) per system.
I tried something else:
Without moving the previously installed wamp's content just read the
"uninstall_services.bat" file
just uninstall these services from that wamp directory which you want to disable.
Still the another wamp's services won't start. So install those services mentioned in "uninstall_services.bat" file manually from respective directories.
Now Restart All Services from the tray icon. The required wamp will be enabled.
If won't, try it again. No need to reinstall wamp.

Spine.js and Hem: Getting started

I successfully created a Spine app as explained on Spine's Getting started page.
However, Hem doesn't automatically take my changes into account; I have to build manually.
I have the same problem when I follow the contact screencast, but this time Hem does not build at all:
art-mac:spine.contacts art$ hem build
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Cannot find module: spine/lib/tmpl. Have you run `npm install .` ?
I did run 'npm install .'
Surprisingly, when I reinstall spine.contact (in another folder), the contacts I created in the previous contact application appear in the new application...
"Disable cash" in my Chrome development settings in is checked.
I was having the same problem when I first upgraded hem to version 0.1.9. One thing to check for is if there are compiled application.js and application.css files in the public folder of your application. It seems like when these files already exist hem server would serve those files instead of recompiling from the sources. Once those files are removed hem server would then use the source files to dynamically create the application files.
But this behavior did seem a bit different from older versions of hem. I was able to make a couple of changes to the hem server so that it seem to work as before, in that the hem server would always compile from the source files regardless if the application files already existed. I posted the code changes on a similar issue at the hem github repository https://github.com/maccman/hem/issues/46#issuecomment-6550866, but I'm not sure if its a hem issue or if something changed with the strata web server library that hem uses.
The latest Hem in npm (0.2.7) should solve this issue.
The strata server was having issues serving files dynamically if they already existed.
Hem 0.1.9 (the latest version) is not automatically detecting changes to my spine app when running "hem server"(although "hem watch" seems to be working correctly). I was able to get it working by uninstalling 0.1.9 (npm uninstall -g hem) and installing 0.1.8 instead (npm install -g hem#0.1.8).
Regarding your other issue, spine/lib/tmpl is no longer included in the latest version of spine, so if you want to use the screencast you'll need to install whatever version of spine he is using.