Skip to content

Commit

Permalink
update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
TobiasSekan committed Jan 19, 2021
1 parent 0cbec3b commit 6530983
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 22 deletions.
64 changes: 42 additions & 22 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,31 @@

vsCode extension for Visual Studio solution files (*.sln)

## New in 1.4.0

* CodeLens on project lines for "Project" nested in "Project".
* Show error for project GUIDs that used by another projects.
* Show error for unknown project type GUIDs.
* Show warning for project names that used by another projects.
* Show warning when module words have not correct PascalCase
* For `Project`, `EndProject`, `ProjectSection`, `EndProjectSection`
* And `Global`, `EndGlobal`, `GlobalSection`, `EndGlobalSection`
* Show info for solution folders, when name is used by another projects.
* Show the line number of the other usage in the diagnostic tooltip in nested project definition.
* Check file extension `.vcxitems` too (should be `C++` project)
* Code completion and syntax highlight for keyword `SharedMSBuildProjectFiles`.
* CodeLens on project lines show no "Project type ..." instead of type only.
## New in 1.5.0

New:

* CodeLens - Open project file and project folder from CodeLens on project lines.
* Show Error
* When files paths in `ProjectSection(SolutionItems)` was not found.
* When a configurations under `GlobalSection(ProjectConfigurationPlatforms)` is not defined.
* They must defined in `GlobalSection(SolutionConfiguration)`

Improvements:

* Show warning when project path have a extension, but it is a solution folder.
* Show more useful warning message for more times nested projects.

Changes:

* Found project GUIDs in lower case are now a info instead of an error.
* Rename `Project type` to `Type` to save space in CodeLens line on projects
* Remove leftover from vsCode beginners extension example

Fixes:

* Show warning for all lines with more times nested projects.
* Project path that start with a ".." have no syntax highlight.

## Picture

Expand All @@ -30,20 +41,29 @@ _Color Theme: Dark+ (default dark)_
* Module and snippets
* Keywords and Properties
* Values and constant
* Hover
* For the first four lines (version)
* For keyword `Project`
* CodeLens
* Project lines: Type | (Open) Folder | (Open) File | Nested in "..."
* For all used project GUIDs with action to jump to project line
* Diagnostic
* Show error for GUIDs that are not project GUIDs
* Show error for project files that was not found
* Show error for files that was not found
* Show error for project GUIDs that used by another projects.
* Show error for not defined configurations.
* Show error for unknown project type GUIDs.
* Show warning for GUIDs that are used several times in `Nested Project` declaration
* Show warning for project names that used by another projects.
* Show warning for project filename that differ from project name
* Show warning for project folders that differ from project name
* Show warning for project file extension that differ from project type
* Currently for `.csproj`, `.vcxproj`, `.vbproj` and `.shproj`
* CodeLens
* For project type GUIDs
* For project GUIDs with action jump to project line
* Currently for `.csproj`, `.vcxproj`,`.vcxitems`, `.vbproj` and `.shproj`
* Show warning when project path have a extension, but it is a solution folder
* Show warning when module words have not correct PascalCase
* For `Project`, `EndProject`, `ProjectSection`, `EndProjectSection`
* And `Global`, `EndGlobal`, `GlobalSection`, `EndGlobalSection`
* Show info for solution folders, when name is used by another projects.
* Hover
* For the first four lines (version)
* For keyword `Project`

## Known Issues

Expand Down
Binary file modified docs/readme.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 6530983

Please sign in to comment.