Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The name 'IsDirtyString' does not exist in the current context #281

Closed
dkoshy opened this issue Apr 27, 2023 · 0 comments · Fixed by #282
Closed

The name 'IsDirtyString' does not exist in the current context #281

dkoshy opened this issue Apr 27, 2023 · 0 comments · Fixed by #282
Labels

Comments

@dkoshy
Copy link

dkoshy commented Apr 27, 2023

Describe the Bug

After adding latest stable version(3.0.5) to my project and building below issue is happening.

Error CS0103 The name 'IsDirtyString' does not exist in the current context ..\ThisAssembly.Git.IsDirty.g.cs 19 Active

Steps to Reproduce

Add this library to function app project targeting .net 6.0 framework.

partial class ThisAssembly
{
    partial class Git
    {
        /// <summary>
        /// Gets whether the current repository is dirty.
        /// </summary>
        public static bool IsDirty => bool.TryParse(IsDirtyString, out var dirty) && dirty;
    }
}

Expected Behavior

project should build successfully.

Version Info

.net6.0

@dkoshy dkoshy added the bug label Apr 27, 2023
kzu added a commit that referenced this issue May 5, 2023
A missing feature in NuGetizer (see devlooped/nugetizer#388) caused our dependency on ThisAssembly.Constants to be lost now that it explicitly sets itself as PrivateAssets=all to prevent analyzer propagation to referenced projects.

This scenario (a package reference with PrivateAssets=all AND Pack=true) was not supported by NuGetizer.

We now do, so this bump is enough to fix the issue.

Fixes #281
@kzu kzu closed this as completed in #282 May 5, 2023
kzu added a commit that referenced this issue May 5, 2023
A missing feature in NuGetizer (see devlooped/nugetizer#388) caused our dependency on ThisAssembly.Constants to be lost now that it explicitly sets itself as PrivateAssets=all to prevent analyzer propagation to referenced projects.

This scenario (a package reference with PrivateAssets=all AND Pack=true) was not supported by NuGetizer.

We now do, so this bump is enough to fix the issue.

Fixes #281
@devlooped devlooped locked and limited conversation to collaborators Sep 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant