alrakis/cursor-lang
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 3 Wiki Activity

modified layout
Pull request / build (pull_request) Successful in 38s
Details

Browse Source
This commit is contained in:
alex
2026-08-12 19:19:18 +05:00
parent 55ac8e6556
commit 7658f01a27
14 changed files with 376 additions and 415 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+21 -7
View File
@@ -166,9 +166,11 @@ An app installed from the Store has no updates section at all: the Store
updates it, and a package from the side is something Windows would not accept
over it anyway.
By itself the app asks about releases once a day, at startup, and remembers the
date of the last successful check in the settings. The check can be turned off
there, which leaves the button in the settings window doing the same on demand.
The app asks about releases every time the settings window appears, and the
answer stays in the section as it is — an unreachable network included. Opening
that window is a deliberate act, rare enough for a request to cost nothing, so
nothing is remembered between openings and there is nothing to turn off. The
button next to the version asks the same question again on demand.
Where the releases are looked for is set in `UpdateOptions` — the repository
belongs to whoever publishes the app, not to the user, so the values live in the
@@ -277,10 +279,22 @@ to Partner Center as it is.
The app ships with its own copy of .NET: Windows does not include .NET 10, and
MSIX cannot install a runtime as a package dependency.
To try the package without installing it, register the published layout — this
needs Developer Mode and no signature at all:
To see the package working on this machine, build it with `-Install`:
```powershell
Add-AppxPackage -Register artifacts\layout\x64\AppxManifest.xml
Remove-AppxPackage (Get-AppxPackage -Name CursorLang).PackageFullName
pwsh -File Packaging\build-msix.ps1 -Architectures x64 -Install
```
The application then shows up in the Start menu like any installed one. What
gets registered is the layout the package is made of rather than the package
file, so no signature is needed — only Developer Mode. The flip side is that the
application runs straight out of `artifacts\layout`, and a rebuild would pull
the files out from under it; the script removes such a registration before it
wipes the folder, whether or not `-Install` was asked for. A copy installed from
the Store answers to the same name and is left alone.
To remove it by hand:
```powershell
Remove-AppxPackage (Get-AppxPackage -Name AleksandrNeychev.CursorLang).PackageFullName
```