Saga 1-v6

[Julia Kozub]

Inprevious version, using Automatonymous required an additional package, MassTransit.Automatonymous. The contents of that package are nowincluded in the MassTransit assembly/package, which now depends on Automatonymous. This was done to reduce the number of extra packagesrequired for container support (along with state machine registration), as well as improve the saga repository persistence assemblies.

If you are using a container with MassTransit, and were using one of the old container packages for Automatonymous, those package referencesshould also be removed. With version 6, only the single container integration package is required (such as MassTransit.Autofac orMassTransit.Extensions.DependencyInjection).

The saga repositories have been completely refactored, to eliminate duplicate logic and increase consistency across the various storage engines. All repositories also now support the container registration extensions, which provides a consistent syntax for registering and configuring saga repositories for use with dependency injection containers. When using the .AddMassTransit() container registration method, a repository can now be registered with the saga. For details, see the updated documentation.

The previous (now legacy) MassTransit.AzureServiceBus package, which was only maintained to continue support for .NET 4.5.2, has been deprecated. Going forward, the MassTransit.Azure.ServiceBus.Core package should be used. The package supports both .NET 4.6.1 and .NET Standard 2.0. With the new package, the .NET Messaging protocol is no longer supported. The new package includes both AMQP and WebSocket support. Certain corporate firewall configurations that previously used .NET Messaging instead of AMQP may need to specify the web socket protocol to connect to Azure Service Bus.

As of version 6, MassTransit now uses DiagnosticSource for tracking messaging operations, such as Send, Receive, Publish, Consume, etc. An Activity iscreated for each operation, and context-relevant tags and baggage are added.

When MassTransit underwent a major overhaul, and multiple host support was added, that seemed like a great idea. A single bus talking to more than one broker, doing messaging. Reality &emdot; nobody used it. It added a lot of complexity, that wasn't used.

With version 6, a single bus has a single host. That's it. Simple. And with this change, it is no longer necessary to specify the host when configuring a receive endpoint. Yes, the old methods are there, and a pseudo-host is returned from the .Host() call which can still be passed, but it is ignored. All the transport-specific configuration methods are still there, without the host parameter.

To be consistent with the rest of MassTransit, many of the interfaces in Courier has been renamed. For example, ExecuteActivity is nowIExecuteActivity. The previous interfaces are still supported, but have been marked obsolete.

Previous version of MassTransit provided a generalized service host, built using Topshelf, to get started with your first project. But the world has changed. With ASP.NET Core 3.1, and all the goodness that is the generic host, the developer community has moved to a new place.

This mission is slightly harder - your goal is to design and deploy two or more comsats to geostationary orbits from your Shuttle and to return to Kerbin. Additional goals are required for higher-ranking badges. Geostationary orbits are circular equatorial orbits with an altitude of 2,863,334.06 m and a period of 5h 59m 9.425s - it's typically easier (and more important) to adjust the period length than to get both the Ap and Pe to the exact same value. More information here

Your mission is to establish a refinery capable of extracting raw ore, refining it into fuels, and preparing it for transport to Kerbin orbit. To this end, fuels are to be stored in modular pods that can be swapped in and out. The SAI 40t Fuel Pod from STS-1b/2b is the prototypical pod, but you may also design your own. Flavors - er, fuel types - are up to you, but keep in mind that you will eventually need to supply a mixture of deep space vehicles, landing craft, probes, etc. The fuel pods are to be transported by a Kerbin-Minmus tanker vehicle which you will launch on a later mission.

Construct your refinery at the location scouted in MINMUS STS-1. After delivering each module with your shuttle, return home, capturing however you like and landing where you want. Prior to the last shuttle departing from Minmus, demonstrate the refinery's operational readiness by refueling the shuttle.

After delivering each module with your shuttle, return home, perform an aero-capture and land at either at the KSC runway, the Island Airfield off the KSC coast, the Dessert Airfield from MH, or at any Kerbal Konstructs airport. Prior to the last shuttle departing from Minmus, demonstrate the refinery's operational readiness by refueling the shuttle.

The Minmus refinery is up and running, but the fuel still needs to get to Kerbin. Your mission now is to solve that problem. You will need an orbital refueling facility to store fuel pods shipped from Minmus, and a tanker ship to do the shipping (yo, dawg). After the initial launch, the tanker is not expected to land on Kerbin, only at the Minmus refinery.

NOTE: You may launch 1 support package for your shuttle using a traditional rocket or shuttle launch for this mission. This support package is limited to delivering components for the refueling facility, tanker, and/or empty fuel pods, to LKO only.

Launch the orbital refueling facility with a shuttle and prepare it for use. Launch the tanker with a second shuttle and prepare it as well, making sure to load it with its maximum complement of empty fuel pods. After each mission, return home, capturing however you like and landing where you want. Demonstrate your fuel transport capability by taking the tanker to Minmus, filling the fuel pods, returning to LKO, and transferring the pods to the refueling facility.

Launch the orbital refueling facility with a shuttle and prepare it for use. Launch the tanker with a second shuttle and prepare it as well, making sure to load it with its maximum complement of empty fuel pods. After each mission, return home, perform an aero-capture and land at either at the KSC runway, the Island Airfield off the KSC coast, the Dessert Airfield from MH, or at any Kerbal Konstructs airport. Demonstrate your fuel transport capability by taking the tanker to Minmus, filling the fuel pods, returning to LKO, and transferring the pods to the refueling facility.

Good luck, and may the shuttles here bring you as much joy as the ones in the previous version brought me! And who knows, after I manage to cure my burnout, maybe I'll come for the badges I did not have the chance to claim myslef as the challenge admin....

An SSTO-capable shuttle with boosters attached has been ruled acceptable in the past, so that's fine. Ion engines are ok if you want, but you may find the burn times hard to deal with. And while a few missions don't require a payload, keep in mind that the primary purpose of a shuttle is to haul heavy and/or complex equipment to orbit and beyond. Then again, you can build an entirely new shuttle each time if you like (I'm working on #5 personally).

I didn't get a chance to address this in the last thread before it was closed. Sorry, but I must insist that you complete STS-2a before posting new missions. I have to maintain some order around here, after all.

As for your ideas for new challenges, you and anyone else are free to submit a proposal. I cannot promise that I will use your ideas, but I will take them into consideration. I've also had a conversation with michal.don about his ideas that he didn't have a chance to implement.

While original SMM design have proven to be reliable tool in the space exploration it nevertheless felt short of its initial goals. SMM01, SMM02, SMM03 of type 1 are not planned to be retired any time soon. Type 1 most likely would be the first crewed ships to reach as far as Jool. But SMM04 Lapis Livi felt short of its initial design. It has proved to be expensive toy for station resupply missions and after dozen or so automated missions was mothballed and later cannibalised for parts to create next SMM in the line.

SMM05 Vita Vibius is actually 6th ever built Starplane. The first one was lost sub-orbital prototype SMM-P (report states: "Prototype was lost to an outstanding showcase of piloting skills by the test pilot").

Vita Vibius is officially designated as type 3 and it has extended cargo bay that meets original specifications for SMM program. Type 3 has bigger volume of cargo payload as it proven essential during Mun lunches by the type 1. Also after Aurora Arbore IX investigation Kerbal Security Committee is strongly opposed to usage of forward cargo payload on SMM as insecure and reckless cost-cutting feature.

Vita Vibius re-imagines power section that initially was "strap on with of the shelf sub-orbital jet engines" solution for SMM type 1. Type 3 have custom engine design that do have oxidizer afterburner for more versatility. In this design 4 CR-7 are combined with 4 J-404 and allow for good performance in subsonic and supersonic speeds.

Some advancements in the crew security were made. While majority of the crew still have one-way ticket if anything goes south, SMM now have double cockpit and both commander and pilot now can eject from doomed Starplane.

And with some spare old Heavy Launch System boosters Vita Vibius launched itself to eccentric LKO. From there by using only its own orbital engine block she have made to 1/3 synchronous KSO via several burns. After that every orbit relay satellite was launched and boosted by own propulsion to circular KSO.

And during aero breaking it started to be clear that Vita Vibious is falling short of Desert airfield, so KSA suggested Summer Kerman to pilot to Tundra Space Center. Bill have confirmed course of action and ordered sharp maneuver to TSC.

3a8082e126