Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Conversation

@Anipik
Copy link

@Anipik Anipik commented Aug 23, 2018

No description provided.

@Anipik Anipik requested review from danmoseley and jkotas August 23, 2018 20:42
<Link>Common\Interop\Windows\Interop.RegistryOptions.cs</Link>
</Compile>
<Compile Include="$(CommonPath)\CoreLib\Interop\Windows\Kernel32\Interop.RegistryValues.cs">
<Link>Common\CoreLib\Interop\Windows\Kernel32\Interop.RegistryValues.cs</Link>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All registry APIs are defined in Advapi32. The related constants should be defined in Advapi32 as well. I do not think we want to be moving these to Kernel32.

(I am sorry that I have not caught this in the previous PR.)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

np i will move everything to kernel32

Copy link
Member

@jkotas jkotas Aug 23, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to say Advapi32 ?

@Anipik
Copy link
Author

Anipik commented Aug 25, 2018

@dotnet-bot test Linux x64 Release Build

<Compile Include="$(MSBuildThisFileDirectory)System\Numerics\Vector_Operations.cs" />
</ItemGroup>
<ItemGroup Condition="$(TargetsWindows)">
<Compile Include="$(MSBuildThisFileDirectory)Interop\Windows\Advapi32\Interop.RegistryValues.cs" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be in the block with other registry APIs?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file was earlier included irrespective of the value of enableWinRt variable where as all other registry files are include is this property is not true ?
is it fine to move there ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be fine. I do not see any problem with it.

internal const int STANDARD_RIGHTS_READ = READ_CONTROL;
internal const int STANDARD_RIGHTS_WRITE = READ_CONTROL;
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it may be better to move this whole file to CoreLib, and not split it into a bunch of little files. All these constants are likely going to be used together. They are needed in CoreLib - they are under different names in CoreLib right now.

internal const int STANDARD_RIGHTS_WRITE = READ_CONTROL;
}

internal partial class RegistryValues
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: You can make all these static while you are on it.

@Anipik
Copy link
Author

Anipik commented Aug 25, 2018

@dotnet-bot test Linux x64 Release Build

// See the LICENSE file in the project root for more information.

internal partial class Interop
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file has more than RegistryOptions. Call it Interop.Registry.Constants.cs ?

@jkotas
Copy link
Member

jkotas commented Aug 26, 2018

LGTM modulo one nit.

@danmoseley danmoseley merged commit 39c4ddf into dotnet:master Aug 27, 2018
@jkotas
Copy link
Member

jkotas commented Aug 27, 2018

@Anipik CoreLib mirror seems to be stuck.

dotnet-maestro-bot pushed a commit to dotnet-maestro-bot/coreclr that referenced this pull request Aug 27, 2018
* using local copy of registryvaluekind and advapi32

* Moving complete file to shared

* name changed

Signed-off-by: dotnet-bot <[email protected]>
@Anipik
Copy link
Author

Anipik commented Aug 27, 2018

there were some merge conflicts due to da6117f#diff-a5e9bf1aea7b21e5dc1325dc67d264fc
i have resolved them

dotnet-maestro-bot pushed a commit to dotnet-maestro-bot/corert that referenced this pull request Aug 27, 2018
* using local copy of registryvaluekind and advapi32

* Moving complete file to shared

* name changed

Signed-off-by: dotnet-bot <[email protected]>
Anipik added a commit to dotnet/corert that referenced this pull request Aug 27, 2018
* using local copy of registryvaluekind and advapi32

* Moving complete file to shared

* name changed

Signed-off-by: dotnet-bot <[email protected]>
jkotas pushed a commit to dotnet/coreclr that referenced this pull request Aug 27, 2018
* using local copy of registryvaluekind and advapi32

* Moving complete file to shared

* name changed

Signed-off-by: dotnet-bot <[email protected]>
@karelz karelz added this to the 3.0 milestone Sep 6, 2018
@Anipik Anipik deleted the valueKind branch February 26, 2019 19:30
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
* using local copy of registryvaluekind and advapi32

* Moving complete file to shared

* name changed


Commit migrated from dotnet/corefx@39c4ddf
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants