Unable to install/use dotnet framework.

Related to #27

I am having this same issue OliverRC was having in the previous issue. We have kind of a weird configuration though:

We are setting up docker containers that will work as build agents using the teamcity docker image. We’re installing some dependencies inside of that container, one of them being autorest.

autorest seems to install correctly but upon invoking it during a dotnet build, we receive the following:

EXEC : error : Package '@microsoft.azure/autorest.typescript' - '2.0.367' failed to install: [/root/git/services/Api/Api.Client.csproj]
    dotnet-2.0.0@1.4.4 postinstall: node -e "/*PostInstall: Installs platform-specific .NET framework */try{require('./dist/app.js')}catch(e){}"
  Exit status 1

The real issue seems to be during the post install script for the dotnet-2.0.0 package, so this might be better suited for that github repo.

Node version: 8.11.3 npm version: 5.7.0 OS: Ubuntu 16.04

installing dotnet-2.0.0 directly throws the same error.

I have attempted @fearthecowboy’s recommendation from the previous issue and installed autorest globally and ran autorest --reset

[csinge]

I had this similar issue on Windows and fixed it by

• removing dotnet core 2.0 runtime (since I had the 2.1 SDKs anyways)
• Removed autorest via npm and then used yarn instead

npm remove -g autorest

My project setup look like this

{
  "scripts": {
    "postinstall": "./node_modules/.bin/autorest --reset",
    "start": "./node_modules/.bin/autorest --clear-output-folder --input-file=http://localhost:51462/swagger/v1/swagger.json --csharp --output-folder=autogen/csharp --namespace=Test.Utils"
  },
  "dependencies": {
    "autorest": "^2.0.4280"
  }
}

[disophisis]

Weirdly, going down the yarn route has worked out for me. It seems that I had an npmrc folder in /usr/etc. Deleting that directory seems to have fixed things. I’m not sure why that directory being there was causing problems, though. Yarn’s --verbose switch is what led to me discovering that.

Prior to deleting the directory, I tried setting permissions on it, but it didn’t seem to make any difference.