How To Debug Servicestack Integration Tests On Visual Studio For Mac

• How To Debug Servicestack Integration Tests On Visual Studio For Mac Download

Nov 16, 2017  Real time test discovery is a new Visual Studio feature that uses a Roslyn analyzer to discover tests and populate the test explorer in real time without requiring you to build your project. This feature has been introduced in Visual Studio 2017 15.5 Preview 2 behind a feature flag.

This page has moved to The primary and most popular language supported is C#, providing a flexible alternative than sharing your DTO assembly with clients, now clients can easily add a reference to a remote ServiceStack instance and update DTO's directly from within VS.NET. This also lays the groundwork and signals our approach on adding support for typed API's in other languages in future. Add a to prioritize support for it sooner! Our goal with Native Types is to provide an alternative for sharing DTO dlls, that can enable a better dev workflow for external clients who are now able to generate (and update) Typed APIs for your Services from a remote url - reducing the burden and effort required to consume ServiceStack Services whilst benefiting from clients native language strong-typing feedback. The easiest way to Add a ServiceStack reference to your project is to right-click on your project to bring up Add ServiceStack Reference context-menu item. This opens a dialog where you can add the url of the ServiceStack instance you want to typed DTO's for, as well as the name of the DTO source file that's added to your project.

After clicking OK, the servers DTOs and NuGet package are added to the project, providing an instant typed API: With the C# code generated on the Server, the role of Add ServiceStack Reference is then just to integrate the remote C# DTOs into the clients VS.NET project. This is just getting the generated DTOs from the server with default options set by the server and adding them locally to your project within Visual Studio. Update ServiceStack Reference If your server has been updated and you want to update to client DTOs, simply right-click on the DTO file within VS.NET and select Update ServiceStack Reference. Consuming Services from Mobile Clients Thanks to PCL Support, it can also be used from within supported client platforms. Here's a quick Android demo of adding a ServiceStack reference to and consuming one of StackApi's Services: DTO Customization Options The header comments in the generated DTOs allows for further customization of how they're generated where ServiceStackVS automatically watches for any file changes and updates the generated DTOs with any custom Options provided.

How To Debug Servicestack Integration Tests On Visual Studio For Mac Download

Options that are preceded by a C# single line comment // are defaults from the server that can be overridden, e.g. /. Options: Date: 2015-10-07 11:01:27 Version: 4.046 BaseUrl: //GlobalNamespace: //MakePartial: True //MakeVirtual: True //MakeDataContractsExtensible: False //AddReturnMarker: True //AddDescriptionAsComments: True //AddDataContractAttributes: False //AddIndexesToDataMembers: False //AddGeneratedCodeAttributes: False //AddResponseStatus: False //AddImplicitVersion: //InitializeCollections: True //IncludeTypes: //ExcludeTypes: //AddDefaultXmlNamespace:./ To override these options on the client, the // has to be removed. For example, if we did not want our classes to be partial by default for the C# client, our options would look like below. /. Options: Date: 2015-10-07 11:01:27 Version: 4.046 BaseUrl: //GlobalNamespace: MakePartial: False //MakeVirtual: True //MakeDataContractsExtensible: False //AddReturnMarker: True //AddDescriptionAsComments: True //AddDataContractAttributes: False //AddIndexesToDataMembers: False //AddGeneratedCodeAttributes: False //AddResponseStatus: False //AddImplicitVersion: //InitializeCollections: True //IncludeTypes: //ExcludeTypes: //AddDefaultXmlNamespace:./ Options that do not start with a // are sent to the server to override any defaults set by the server. Change Default Server Configuration The above defaults are also overridable on the ServiceStack Server by modifying the default config on the NativeTypesFeature Plugin, e.g.

assembly: ContractNamespace( ', ClrNamespace = 'StackApis.ServiceModel.Types ') assembly: ContractNamespace( ', ClrNamespace = 'StackApis.ServiceModel ') Requires AddDataContractAttributes=true Xamarin Studio With the new your Service Consumers can now generate typed DTOs of your remote ServiceStack Services directly from within Xamarin Studio, which together with the ServiceStack.Client NuGet package provides an effortless way to enable an end-to-end Typed API from within Xamarin C# projects. Installing ServiceStackXS Installation is straightforward if you've installed Xamarin Add-ins before, just go to Xamarin Studio - Add-In Manager. From the Menu and then search for ServiceStack from the Gallery: Install from file If you are having trouble with the Xamarin Studio gallery version, you can install addins from an mpack file from the same menu as shown above. Click Install from file and navigate to where you have downloaded the mpack file.

Adding a ServiceStack Reference Once installed, adding a ServiceStack Reference is very similar to where you can just click on Add - Add ServiceStack Reference. On the project's context menu to bring up the familiar Add Reference dialog. After adding the BaseUrl of the remote ServiceStack instance, click OK to add the generated DTO's to your project using the name specified: Updating the ServiceStack Reference As file watching isn't supported yet, to refresh the generated DTOs, you'll need to right-click on it in the solution explorer and select Update ServiceStack Reference from the items context menu.

Xamarin Studio for Linux One of the nice benefits of creating an Xamarin Studio Add-in is that we're also able to bring the same experience to.NET Developers on Linux! Which works similar to OSX where you can install ServiceStackXS from the Add-in Gallery - Here's an example using Ubuntu: Then Add ServiceStack Reference is accessible in the same way. Getting Started. Designing APIs. Reference.

Clients. Formats. View Engines 4. Hosts. Security. Advanced.

Caching. Auto Query. Server Events. Service Gateway. Encrypted Messaging. Plugins.

Tests. ServiceStackVS. Other Languages.

Amazon Web Services. Deployment.

Install 3rd Party Products. Use Cases. Performance. Other Products.

Future. Clone this wiki locally.

Greetings fellow geeks! This week's pain sharing experience was brought to you by the age old 'buy versus build?' , 'commercial versus open source?' Debate that has consumed the software development world for many years.

This week, we score a win for open source. When you support a commercial application that has dependencies on commercial and open source APIs, you always have to be on your toes not knowing what can crop up from within your dependencies stack. So there we were in the midst of a load test, when all of a sudden, we get this fine gem of an error The free-quota limit on '6000 Redis requests per hour' has been reached. Please see to upgrade to a commercial license. After a little research, it became clear that ServiceStack decided to go from open source, to commercial, as they went from v3 to v4 of their API library. Hey, you know what?

Good for them, they built something in high enough demand that people are willing to pay for it. Well, it would have been nice to make a smooth transition for teams that had already committed to their open source solution not realizing that now, it was going to cost money. 'Annual budgets' and 'all of a sudden' do NOT work well together. So, this officially becomes an application architecture issue, ball is in my court. After frantically looking for a solution as solution developers do, I had 3 options. Pay. Downgrade from v4 to v3.

Find a new API and make a code change to transition to it. Two problems with Pay.

One, end of fiscal year, pay would be an uphill battle. Two, the reasoning of 'why pay?' Is tough to stomach. How is something that was free 'all of a sudden' thousands of dollars? I don't ever recall intentionally downgrading software. So, as out of touch with that practice as I am, it didn't sound like the best solution.

3 days left in the Sprint. In a class that was called upon more often than any other class. 'Spidey sense' was working overtime on that one. So, downgrade started to look like the path of least resistance. After half a day of fighting with the downgrade, I discovered that the packaged dependencies had several issues. 1 Method 'getDb' in type 'ServiceStack.Redis.RedisNativeClient' from assembly 'ServiceStack.Redis, Version=3.9.71.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

And then this. After fighting through packaging issues, the API wasn't compatible so code changes were still required!!! And then, the icing on the cake. V3 did not support secure communication (SSL).

Great, 2.5 days left, new API it is. 24 hour work mode. Since Azure Redis Cache was the server side to this operation, there was some documentation around an open source API, StackExchange.Redis Problem with this library, out of the box, no object support. We were persisting objects using the ServiceStack library.

I even tried building object support around it, but our objects were quite complex and I didn't want to walk the path of building an entire library. This discovery effort ate up another 1.5 days!!! A little more scouring, and then I found it!

Thank you, Imperugo!!!! This required a standalone config section in the config file. A small and easy requirement. Then, it required a serializer. Low and behold, here's one! The only gotcha with that library is there's a pretty good chance you're already using Newtonsoft, so as long as you're OK with upgrading the version, you should be good to go. In my dwindling hours of desperation, I upgraded Newtonsoft.

Ran all my unit tests and good to go! In closing, sometimes the path of least resistant takes time away from the better, longer term solution.

I suppose I should warn about a possible sequel when the StackExchange library goes commercial.:) Happy Coding!