Navigation Menu

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

Include AllowPartiallyTrustedCallers in C# code again #552

Closed
jskeet opened this issue Jun 29, 2015 · 0 comments
Closed

Include AllowPartiallyTrustedCallers in C# code again #552

jskeet opened this issue Jun 29, 2015 · 0 comments
Assignees
Labels

Comments

@jskeet
Copy link
Contributor

jskeet commented Jun 29, 2015

Removed in commit ce97e68, but assuming it's available in our PCL target profile, we should re-add it.
(If it's not, we'll have to take a close look...)

@jskeet jskeet added the c# label Jun 29, 2015
@jskeet jskeet self-assigned this Aug 3, 2015
jskeet added a commit to jskeet/protobuf that referenced this issue Aug 3, 2015
Fixes issue protocolbuffers#552. (And yay, it looks like our build profile supports this...)
@jskeet jskeet closed this as completed Aug 3, 2015
taoso pushed a commit to taoso/protobuf that referenced this issue Aug 1, 2018
Move _conformance directory to conformance. (The _ was apparently there
to prevent "go install ./..." from touching that directory, which
doesn't seem like a sufficient reason to have a weird path name.)

Delete conformance_proto directory, regenerate the proto at test time.
(This proto is used for communications between the test runner and test
process; nothing else needs it.)

Add a list of known failures.

Add a Makefile so that "make test" in the conformance directory does the
right thing. (Requires that github.com/google/protobuf be installed
somewhere.) Include documentation in "make all" output. Skip tests if
the necessary dependencies don't exist.
rinarakaki pushed a commit to rinarakaki/protobuf that referenced this issue Aug 30, 2023
bithium pushed a commit to bithium/protobuf that referenced this issue Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant