dotnet / dotnet.github.io Goto Github PK

The terminal prompt (e.g. ~$ or PS >) shouldn't be included when copying/pasting from the getting started page.

One option to fix this is to just get rid of the terminal prompt. Another option is to format the commands as a table with the terminal prompts in one column and the commands in a second column. There might be other fixes too.

At least for me it looks a bit bad. This black and white rectangle on each button when I push it to see manual.
(Wasn't able to take a pic, but I think it's clear how it looks by default :P)

It's just my opinion. I think it's better when they are highlighted without Moz selection.

For the .NET Core getting started page, be cool if we automatically displayed instructions related to the operating system you are browsing from - i.e. browsing on a Mac, have Mac instructions selected rather than Linux etc.

http://dotnet.github.io/core/getting-started/

/cc @blackdwarf

I just browsed the .NET Core page and here are some feedback items that crossed my mind:

• No "View Source" button. It's very difficult finding a link to the actual github repository, I'd suggest placing a button next to "Getting started" and "About .NET Core"
• The gif that is supposed to show .NET Core in action is way too fast, I can't see what's going on. It should also wait a couple of seconds at the end before starting the loop again.
• There's some dithering/quality issues in the gif, which program did you use to capture it? I had very good results with licecap.
• The Windows install steps mention powershell (PS), but the command only works in CMD, see https://github.com/dotnet/coreclr/issues/1132
• The Mac install steps have a typo: brew tupdate

Other than those, the page looks very nice 👍

/cc @blackdwarf

The link on the getting started page downloads an msi that does not have a valid digital signature. Is that by design?

https://dotnet.github.io/getting-started/
https://dotnetcli.blob.core.windows.net/dotnet/dev/Installers/Latest/dotnet-win-x64.latest.msi

In the footer of the page, the Twitter and facebook icons are absents, probably not implemented.

Hi,

The dotnet repository is signed weakly, according to newer (>= 1.2.7)
apt versions. It complains:

W: http://apt-mo.trafficmanager.net/repos/dotnet/dists/trusty/InRelease: Signature by key 52E16F86FEE04B979B07E28DB02C46DF417A0893 uses weak digest algorithm (SHA1)

It seems your repositories are done with aptly. Unfortunately, aptly
does not appear to offer a configuration option, so you'll need to use
a build that includes the following commit:

smira/aptly-fork@1069458

Hopefully this can be fixed, so that users do not get a scary warning
on apt-get update.

Among the download options should be a "build-from-source" option. Even if not used often, it demonstrates that you are open with respect to the source code by featuring the source prominently.

The installer linked in the getting started page is currently broken (or at least broken on my windows version).

This should be fixed as it's a bad "first contact" and because this seems like the suggested version.

14:39:57 C:\git\dotnet\try\src\stuff >
# dotnet new
Created new C# project in C:\git\dotnet\try\src\stuff.
14:40:01 C:\git\dotnet\try\src\stuff >
# dotnet restore
Exception has been thrown by the target of an invocation.
14:40:06 C:\git\dotnet\try\src\stuff >
# dotnet --version
.NET Command Line Tools (1.0.0-beta-001598)
Product Information:
Version: 1.0.0-beta-001598
Commit Sha: 7582649f88
Runtime Environment:
OS Name: Windows
OS Version: 6.3.9600
OS Platform: Windows
Runtime Id: win81-x64

The instructions on the dotnet core site need to be updated, since brew is no longer the correct way to get dnvm on OSX
Related to the aspnet/dnvm#485

Sorry in advance if this not the appropriate place to post this issue.

How to execute cleanup code on Dispose event of System.Diagnostics.Process? Could you please point out if there is a different way of doing this?

The redirect to https://dotnet.microsoft.com doesn't work on the subpages.

Pages like https://dotnet.github.io/dotnet-web/ are still available.

Problematic is, that Google has some pages in the top result:

Link: https://dotnet.github.io/dotnet-web/docs/porting/supporting-core.html

(This may not be the right place for this post, but I have no idea where else to put it)

I really feel like the wider vnext project needs someone to own a global 'Getting started with RC1' manual - perhaps on [docs.aspnet.org], that is directed to from all current documentation areas/packages.

I know a lot is going on with the move to dotnet, but I have literally spent hours and hours and hours trying to make sense of everything. From what I've seen of the milestones, RC2 is months away and therefore this would probably be worthwhile.

It took me hours to realize (as a brand new vnext user as of a week ago):

• RC1-final is best to work with right now
  • because of huge (good) changes across the board undergoing in RC2
  • because RC2 seems months away (which is fine)
• It's easiest to stick with dnx451 or dnx46 native frameworks right now
• AspNetCore.* dependencies use a new namespace for RC2+, and I should be using AspNet.* packages instead
• Packages are managed most easily in Visual Studio via the context menu 'Manage packages'
• Adding the non-standard URL to the package manager in VS was required to get RC2 packages
• Look at code samples in master branches are probably for RC2, better to refer to release* or RC1-* branches
• RC2 packages need a custom package provider setting up
• dotnet replaces dnx, dnvm etc
• dotnet is essential for RC2+
• dotnet is not essential for RC1, can use dnx etc at the time (not clear from package repos)
• dnx46,dnx451 are .NET Native frameworks
• dnxcore50 is RC1* name for .NET Core
• project.json schemas documented had slight differences between RC1, RC2
• The official documentation website shows 'vnext' as the default, which seems to be RC2 related.
• Using dnxcore50 as a framework doesn't seem to work easily because it needs ".NET Native" libraries - how do I make it use these?

I could go on. Instead of making stuff, I've been running around in circles. I know vNext is new, but RC1 should be easier to get going with.

What would clear this up:

• Explain how and why RC1 is what most people should use right now
• Getting started with RC1
• Explain who should use RC2
• Getting started with RC2

If RC2 was ready tomorrow, I wouldn't bother with this post, but it seems months away. Which is fine because the changes are great and clarify so much with this project.

@shanselman identified several things that should make the .NET Core site much better:

• Introduce better URLs by getting rid of the *.html extensions.
• Fix the Mono explanation on Linux getting started instructions.
• Have a default starting "trail" on the Getting Started page.

I will be making a PR soon with these changes.

/cc @richlander @akoeplinger @martinwoodward

As per dotnet/cli#1286, there is no support in NuGet xplat client for encrypted passwords. If users have a global NuGet.config file which has a feed with this, dotnet restore will blow up. The getting started guide needs to warn about this for now, until NuGet implements a better error.

As per https://docs.asp.net/en/latest/getting-started/installing-on-mac.html, DNVM is not being distributed as a brew recipe anymore.

There is probably a reason for not doing this. so, I wanted to open this issue rather than sending a PR. It would be really good to include how to install dotnet CLI through PowerShell (just like dnvm). For example, I used the below script which did the trick except for adding it to my PATH (copy from aspnet/Home repo):

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "&{$Branch='dev';$wc=New-Object System.Net.WebClient;$wc.Proxy=[System.Net.WebRequest]::DefaultWebProxy;$wc.Proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials;Invoke-Expression ($wc.DownloadString('https://raw.githubusercontent.com/dotnet/cli/master/scripts/obtain/install.ps1'))}"

Community includes the GitHub repos. Right now, the links to the GitHub repos are buried and should be featured more prominently. One way to do this is include the GitHub repo links on the Community page.

When trying to follow the Getting Started guide on dotnet.github.io, I'm getting the following exception

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.IO, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

   at System.Console.WriteLine(String value)
   at HelloWorldSample.Program.Main()

I resolved this by adding the following dependency

"System.IO": "4.0.11-beta-*"

I don't believe this is something specific to my system, I will open a pull request for the docs.

They need to point to install script and explain the steps there.

If you select Docker as your option on Getting Stated page, it shows steps like 1, 2, 2, 3. Not sure if its intentional or not.

When i google/bing install .net core sdk, i get to the following landing page:
https://www.microsoft.com/net/core#windows, with the following instructions

    [.NET Core 1.0.0 - VS 2015 Tooling Preview 2](https://go.microsoft.com/fwlink/?LinkID=824849)

You can also develop .NET Core apps from the command-line by downloading the [.NET Core SDK for Windows](https://go.microsoft.com/fwlink/?LinkID=809122). You can use your own editor, or with Visual Studio Code (free).

Both https://go.microsoft.com/fwlink/?LinkID=824849 and https://go.microsoft.com/fwlink/?LinkID=809122 installs only for x64 and that too a very old version of CLI

The above installed CLI has a lot of missing features like publishing portable apps. The links should be fixed.

The correct link could be https://www.microsoft.com/net/download

what should be done to fix it ?
If this is not the correct place to file the issue, where should i file it ?

cc @gkhanna79

Add information about porting and pointers to various porting tools to the Core website under /porting/.

Minor nit: After installing the DotNetPackage and OpenSSL, you need to restart the terminal to get dotnet commands resolving. Tried looking for a md file to update and all I found was the HTML. Let me know if I should raise a PR.

Should probably be something else.