Closed vimarx closed 2 years ago
I tried a few times in the past but failed, however happy to default to a dark skin
We will try to answer all questions that do not require research within 24hr. To prioritize cases that require research we use the following labels in order. For all other issues the posting time is respected.
This case is prioritized.
eXpand.lab release 20.2.402.3 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Thanks a lot for your contribution.
Sorry, I think it is now the other way around.
yes true, although I really recommend you relax your eyes with a dark theme, we need to default it to white and add a manual parameter in the otions to chnage to dark if u want. As I say I cannot find a way to detect the VS current there so to automate it.
OK, I relax...... ;-)
eXpand.lab release 20.2.500.0 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Thanks a lot for your contribution.
eXpand.lab release 20.2.502.1 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Thanks a lot for your contribution.
Hi, there is an own setting and it works.
Hi,
Not sure what u mean
Issue is deprioritized
as no Assignee found
and scheduled for auto-close
if no activity in the next 60 days
. Thanks a lot for your contribution.
Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.
𝗗𝗲𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗵𝗲 𝗯𝘂𝗴