-
Notifications
You must be signed in to change notification settings - Fork 844
adjust dep manager error message in FSI, when extension is not loaded #13029
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hey @smoothdeveloper, do you still think this can be of some use? As of now, the added link leads to the |
|
@psfinaki yes I do think it would be useful, but I don't have control on aka.ms and I am not clear how much Microsoft is interested in endorsing and improving the user story around the extension mechanism. Overall, having the README.md restored in this repository, and aka.ms link pointing to it would be a first step in the right direction. I'm open to other suggestions. |
|
Hmm alright, I'll get to this during this week. |
|
So I've looked at this again, and I propose the following approach. Feel free to add the suggested content to this README with this PR. I think what you've written is useful. Then after we merge this (if no one is against it), I'll add some aka.ms link to the docs, I think I know how to create them. |
|
@smoothdeveloper do you want to add the README to this PR so we can link it with aka.ms? |
|
@0101 yes, and sorry for the previous messages which I didn't see! I'll get over it this weekend. Thanks all! |
…er which isn't loaded in FSI.
…each F# team to update the redirect.
c8504da to
1f63b5d
Compare
|
I've brought back the readme that lists both nuget & paket. If it is ok, we can merge. |
…dance to understand the overall system.
|
I've added pointer to RFC and the implementation detail leveraging reflection, highlighting this uses a late binding mechanism to avoid a static dependency. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
psfinaki
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, I think this is good.
|
Alright @smoothdeveloper, thanks and here you go: aka.ms/dotnetdepmanager :) |
For now, it is just to check the CI.
https://github.com/smoothdeveloper/visualfsharp/blob/16871138b029685c77d55c721a5a54f97f5156d6/src/fsharp/Microsoft.DotNet.DependencyManager/README.md is the content I came up with initially, it was still F# specific.
It would be good, if we clarify the intents, as to what we want to do with the interactive extensions in the broader sense.
My main concern has been the user story, for users to deploy such extensions (and the documentation on that page, for it to not generate support requests, anywhere), if we can't define a canonical and stable location that works across the environments (IDEs, fsi, dotnet interactive, FSC enabled tooling), and FCS isn't making it super smooth to "it just works", then, it is unlikely the ecosystem.
With this in mind, stuff to put on the page:
Having a "list of recommended extensions" on fsharp.org, would also be sensible, where it will be easier for community to maintain, without adding burden to this repository.