Skip to content

Conversation

@vcsjones
Copy link
Member

Summary

The output of the sample program for BlockSize will vary depending on if you run it for .NET Framework or .NET Core for RijndaelManaged (the max block size is 128 in .NET Core, while it is 256 in .NET Framework). This makes note of that difference.

Fixes dotnet/runtime#37127

/cc @bartonjs

@dotnet-bot dotnet-bot added this to the May 2020 milestone May 28, 2020
@mairaw
Copy link
Contributor

mairaw commented Jun 3, 2020

@vcsjones
Copy link
Member Author

vcsjones commented Jun 3, 2020

@mairaw I may be misunderstanding but the PR has changes for both C# and VB?

https://github.com/dotnet/dotnet-api-docs/pull/4300/files#diff-0ce01c0614677250518b7c1dcb4e7032

@BillWagner
Copy link
Member

@vcsjones The snippet file changed in this PR has a corresponding VB file. Those are inputs to the docs build, and the code is rendered in the final page. You should make the corresponding change in the VB file so that both examples contain the update when rendered.

@mairaw
Copy link
Contributor

mairaw commented Jun 4, 2020

My bad @vcsjones! Somehow I missed that.

@mairaw mairaw merged commit 1c2f680 into dotnet:master Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

.NET Core 3.1 - RijndaelManaged - Initialization vector 256 bits not supported

5 participants