- remove references to specific VS versions (these will quickly become
stale and can be confusing because VS wants you to live on the latest
version).
- include mac/linux instructions
This is a hint to tools (and the CLI) about what version of the SDK is
required to work with the repo. This is set up to be as flexible as
possible. 3.1.100 is what's in our instructions already and is the
minimum version usable (since we target .NET Core 3.1).
This spooky XML boilerplate was needed on early versions of .NET Core,
but isn't required in modern versions (we require 3.1.1XX of the SDK
because we target .NET Core 3.1).
Removes generation of documentation files for samples and tests. This is
a vestige from using the older Stylecop tool in this repo, which needs
the doc files to inspect.
The deleterious effect of this is getting warnings about missing
documentation on samples, and forcing contributors and maintainers to
write nonsense comments to workaround the warning.
Also removed references to stylecop, since we no longer use it.
This is a workaround for https://github.com/dotnet/sdk/issues/14019
which prevents the current prerelease dotnet SDK
`5.0.100-rc.1.20452.10` from successfully building the repo.
Users attempting to build with the bugged release will see a compiler
error related to the `System.IO.Pipelines` assembly.
The explicit reference to `System.IO.Pipelines` is harmless long term,
but can be removed when the underlying bug is fixed and shipped in a GA
release (likely 5.0.100 GA).
* Prepping for multi pubsub
* Add pubsub name, some cleanup
* multi pubsub changes
Co-authored-by: Aman Bhardwaj <amanbha@microsoft.com>
Co-authored-by: LM <lemai>
* Add bulk get to client
* change params, return type, class to struct
* change IList to IReadOnlyList, make parallelism nullable
* change GetBulkItem to BulkStateItem
* Use protobuf packaging for the Any type
This pull request implements two converters which help with the type conversion between arbitrary types and the protobuf `Any` type. The C# protobuf library provides a mechanism to pack or unpack protobuf messages to `Any`. It provides the methods `Any.Pack` and `Any.Unpack` to serialize/deserialize messages based on `Google.Protobuf.IMessage`. For types that are not based on `Google.Protobuf.IMessage`, the existing JSON serialization/deserialization will be used.
I've also cleaned the existing codebase a little bit.
Fixes#268
* Fix suggested changes
* added missing dapr port parameter
added version number to 'add package' calls
* Calculator Sample
* Revert "Calculator Sample"
This reverts commit ec4b7af03b.
* add missing hyphen on port param
Co-authored-by: Garret Magin <garretm@microsoft.com>
* removed dll from `dotnet run` call
* updated version to `0.9.0-preview01`
* added note to use latest nuget version
Co-authored-by: Nico Meisenzahl <nico@meisenzahl.org>
Co-authored-by: André Ratzenberger <andre.ratzenberger@whiteduck.de>
Co-authored-by: Garret Magin <garretm@microsoft.com>
* Remove secret store extension from building
* Remove code
Co-authored-by: LM <lemai>
Co-authored-by: Aman Bhardwaj <amanbha@users.noreply.github.com>
* Include the appcallback.proto into the Dapr.Client package
To implement service invocation for a gRPC API, a user must implement the AppCallback service on the callee site. Currently this must be done by integrating the `appcallpack.proto` file as also the depending `common.proto` file into the gRPC service application. The `Dapr.Client` package contains already the same `common.proto` file to generate the client classes. This results in a CS0433 error, because the `Dapr.Client` package and the generated AppCallback service will contain a `Dapr.Client.Autogen.Grpc.v1` namespace with the exact same classes.
This pull requests integrates the `appcallpack.proto` into the client package. With this fix the user does not need to integrate the proto files by itself.
See: https://gitter.im/Dapr/community?at=5f14b7e98a9a0a08cbab5d53
* Remove specific names
- Explicitly specify netcoreapp3.1 on project creation
- Remove documentation section on updating to netcoreapp3.0 which is obsolte
- Fix missing using statements in MyActoreService code updates
* #312 - make changes corresponding to change in dapr runtime. The runtime will no longer send an activate message. The SDK should 'activate' an actor anytime it receives an actor method call
* spaces
* remove comment'
Co-authored-by: LM <lemai>
vinayada1
Ryan Nowak
Young Bu Park
Edwin van Wijk
Mark Fussell
Sander Molenkamp
Leon Mai
Yaron Schneider
Gokhan Altinoren
Aman Bhardwaj
Christian Kaps
wdjhu
Tom Kerkhove
Lars Gyrup Brink Nielsen
Garret Magin