You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEVGUIDE.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,8 +108,8 @@ Running any of the above will build the latest changes and run tests against the
108
108
109
109
If your changes involve modifying the list of language keywords in any way, (e.g. when implementing a new keyword), the XLF localization files need to be synced with the corresponding resx files. This can be done automatically by running
This only works on Windows/.NETStandard framework, so changing this from any other platform requires editing and syncing all of the XLF files manually.
@@ -122,7 +122,7 @@ See (DEVGUIDE.md#Developing on Windows) for instructions to install what is need
122
122
123
123
### Quickly see your changes locally
124
124
125
-
First, ensure that `VisualFSharpDebug` is the startup project.
125
+
First, ensure that `VisualFSharpFull` is the startup project.
126
126
127
127
Then, use the **f5** or **ctrl+f5** keyboard shortcuts to test your tooling changes. The former will debug a new instance of Visual Studio. The latter will launch a new instance of Visual Studio, but with your changes installed.
128
128
@@ -136,7 +136,7 @@ If you'd like to "run with your changes", you can produce a VSIX and install it
It's important to use `Release` if you want to see if your changes have had a noticeable performance impact.
@@ -170,4 +170,9 @@ See the "Debugging The Compiler" section of this [article](https://medium.com/@w
170
170
171
171
If you are behind a proxy server, NuGet client tool must be configured to use it:
172
172
173
-
See the Nuget config file documention for use with a proxy server [https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file)
Copy file name to clipboardExpand all lines: FSharpBuild.Directory.Build.props
-6Lines changed: 0 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -8,19 +8,13 @@
8
8
</PropertyGroup>
9
9
10
10
<!-- directory locations -->
11
-
12
-
<PropertyGroupCondition="'$(OS)' != 'Unix' and '$(DisableAutoSetFscCompilerPath)' != 'true' and '$(Configuration)' != 'Proto' and '$(DOTNET_HOST_PATH)' != ''">
You can use the latest `main` build of the F# compiler and tools for Visual Studio via our nightly releases if you are a Visual Studio user. See details on setup here:
Alternatively, if you _really_ want to live on the bleeding edge, you can set up a nightly feed for the Visual Studio preview releases, which use the latest commit in the preview branch. To do so, follow the same instructions as the above blog post, but instead with these links:
72
+
73
+
* Set your feed to the preview feed: https://dotnet.myget.org/F/fsharp-preview/vsix
74
+
* Install a VSIX manually from the preview feed: https://dotnet.myget.org/feed/fsharp-preview/package/vsix/VisualFSharp
75
+
63
76
## Per-build NuGet packages
64
77
65
78
Per-build verions of our NuGet packages are available via this URL: `https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json `
0 commit comments