-
Updated
Jul 9, 2022 - C#
roslyn
Here are 329 public repositories matching this topic...
-
Updated
Jul 6, 2022 - C#
-
Updated
Jun 25, 2022 - C#
-
Updated
Jul 1, 2022 - C#
-
Updated
Jun 30, 2022 - C#
-
Updated
Jun 23, 2022 - C#
-
Updated
Jan 16, 2022 - C#
-
Updated
Jul 7, 2022
-
Updated
Jun 26, 2022 - C#
-
Updated
May 26, 2022 - C#
Steps to reproduce
-
Have a VB app with XML Documentation checked in project settings, set to \bin\FixityVB.xml
-
Convert to C#
-
Change to release configuration
-
App won't build. Error is:
Error CS2021 File name ‘C:\dev\fixity\FixityVB\bin\’ is empty, contains invalid characters, has a drive specification without an absolute path, or is too long -
Go into project settings, cha
-
Updated
Jul 8, 2022 - C#
-
Updated
May 28, 2022
-
Updated
May 23, 2022 - C#
-
Updated
Nov 27, 2020 - C#
-
Updated
Jul 4, 2022 - C#
-
Updated
Feb 19, 2018 - C#
-
Updated
Jun 27, 2022 - C#
-
Updated
May 31, 2022 - C#
In some limited scenarios, it might be worth switching to static readonly properties (perhaps backed by the private constant) so that updates to the library providing the ThisAssembly don't require recompiling callers in order to get the updated values (since consts are embedded raw in the callsite at compile-time).
This might not be so common since ThisAssembly is (by default) internal and (m
Improve this page
Add a description, image, and links to the roslyn topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the roslyn topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

On which page?
https://platform.uno/docs/articles/guides/uno-material-walkthrough.html
What's wrong?
Step 2 within the "Section 2: Using Uno.Material library" section makes reference to Chip/ChipGroup/Card/Divider which have now all been moved to the Uno.Toolkit.UI.Material package.
These changes will also need to be reflected in the referenced UnoMaterialSample, an issue tracking