Update readme files, remove old information

Author: Rpinski

README.md

@@ -6,7 +6,7 @@ Please see the [Feature Comparison List](https://github.com/icsharpcode/ilspy-vs
 
 ## Getting started
 
-You can [install](https://github.com/icsharpcode/ilspy-vscode/wiki/Installation) the extension in Visual Studio Code via the [marketplace](https://marketplace.visualstudio.com/items?itemName=icsharpcode.ilspy-vscode).
+You can [install](https://github.com/icsharpcode/ilspy-vscode/wiki/Installation) the extension in Visual Studio Code via the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=icsharpcode.ilspy-vscode) or [Open VSX](https://open-vsx.org/extension/icsharpcode/ilspy-vscode).
 
 Please see the [Feature Tour](https://github.com/icsharpcode/ilspy-vscode/wiki/Feature-Tour) to explore the extension's features.
 
@@ -20,13 +20,7 @@ If you have issues during installation of .NET Runtime, please see [here](https:
 
 ## Develop
 
-The extension consists of two parts: The VSCode extension itself (written in TypeScript) and a "backend" server process (written in C#), which provides a bridge to ILSpy functionality.
-
-If first time
-
-```
-npm i @vscode/vsce -g
-```
+The extension consists of two parts: The VS Code extension itself (written in TypeScript) and a "backend" server process (written in C#), which provides a bridge to ILSpy functionality.
 
 Compile and package all parts:
 
@@ -60,3 +54,5 @@ then run
 cd vscode-extension
 code .
 ```
+
+The backend code must have been built at least once (as seen above) for the extension to run.

vscode-extension/README.md

@@ -1,66 +1,37 @@
-# ilspy-vscode (powered by ICSharpCode.Decompiler)
+# ilspy-vscode (Extension)
 
-Welcome to the ILSpy extension for Visual Studio Code! This extension provides two commands inside Visual Studio Code:
+This is the actual VSCode extension part of the project, which fulfills following tasks:
 
-- `ilspy.decompileAssemblyInWorkspace` - Decompile an MSIL assembly inside the current Visual Studio Code workspace.
-- `ilspy.decompileAssemblyViaDialog` - Decompile an MSIL assembly from file picker dialog.
+* Integrates ILSpy UI elements (like Assembly Tree, Search and Analyze panels, palette commands) into VSCode shell
+* Manages extension settings (global and workspace-specific)
+* Controls [backend](../backend/README.md) process launching it at startup and initializing it with configuration
+* Installs a required version of .NET runtime using Microsoft's [.NET Install Tool for Extension Authors](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.vscode-dotnet-runtime)
 
-Open the Visual Studio Code Command Palette (<kbd>Ctrl+Shift+P</kbd>) then type `ilspy` to show the two commands.
-
-The `Decompile IL Assembly in Current Workspace` will put all potential .NET assemblies
-(files with extension `.dll`, `.exe`, `.winmd`, `.netmodule`, `.wasm` or `.nupkg`) in your
-workspace in a list for selection.
-
-The `Decompile IL Assembly (pick file)` command allows choosing an assembly using the file picker dialog. The dialog
-should also allow one to type in the full path, for example, `c:/temp/a.dll` or `/home/user/b.dll`.
-
-If the file is a valid .NET assembly or NuGet package, a tree view named `ILSPY: ASSEMBLIES` is added into the Explorer view.
-It allows expanding and selecting various nodes, whose decompiled C# code is shown in the editor.
-
-Loaded assemblies can be closed by hovering the assemly nodes and clicking the "X" icon.
-
-Further features are:
-
-- Symbol search across all loaded assemblies
-- Decompiling symbols to IL and different C# versions
-- Analyzing references between symbols across loaded assemblies
-- Saving list of loaded assemblies along with currently open workspace
+A description of the extension's features can be found in [Feature Tour](https://github.com/icsharpcode/ilspy-vscode/wiki/Feature-Tour).
 
 ## Requirements
 
 - Visual Studio Code >= 1.101
 - .NET 10.0 (installed automatically on first start)
-
-## What's New
-
-See our [change log](https://github.com/icsharpcode/ilspy-vscode/blob/master/vscode-extension/CHANGELOG.md) for all of the updates.
-
-### Found a Bug?
-
-Please file any issues at https://github.com/icsharpcode/ilspy-vscode/issues
-
-## Development
-
-First install:
-
 - Node.js (22 or newer)
 - NPM
 
-- Compile and prepare ILSpy.Backend:
+## Development
+
+To debug and run the extension, you first need to build and package the backend:
 
 ```
 cd ..
-buildtools/build-backend
+buildtools/publish-backend
 ```
 
-- Run `npm i`
-- Run `npm run compile`
-- Open in Visual Studio Code (`code .`)
-- _Optional:_ run `npm run watch`, make code changes
-- Press <kbd>F5</kbd> to debug
+The backend's binaries are automatically copied to `vscode-extension/bin/ilspy-backend`, where the extension expects them.
+
+Then initialize the project with
 
-To **test** do the following: `npm test` or <kbd>F5</kbd> in VS Code with the "Launch Tests" debug configuration.
+```
+npm install
+```
 
-## License
+Open this directory in Visual Studio Code and start debugging with <kbd>F5</kbd>. A development instance of VS Code will open with the latest extension code running.
 
-[MIT license](https://github.com/icsharpcode/ilspy-vscode/blob/master/vscode-extension/LICENSE.TXT).