Migrate .Net Framework Reliable Services to SF Mesh

[PrabhujiMudragalla]

Hi Team,

We are eager to migrate our application to SF Mesh. I am afraid about about the limitations of SF Mesh.

My application is build up on .Net Framework Service Fabric Reliable services which include following capabilities:

1. Stateful Services with Reliable collections
2. Reliable actors
3. Backup and Restore mechansim
4. Event Grid Messaging

And many more..

All this components are implemented using .Net Framework. So can you provide me a mechansim to migrate all this components without affecting the business.

It would be greatful if you provide the roadmap of SF Mesh. Such that we can plan our deliverables.

Thanks Prabhuji

[tomkerkhove]

Reliable collections & actors are not there (yet) so I think you'll have to wait a while but you can already start running your applications as Windows containers

[abaymar]

Is there a step-by-step guide for creating a yaml/json for SF Mesh that uses my containers? I tried to modify the one produced by Visual Studio for .NET Core containers and I failed.

I already have my .NET Framework containers deployed to Azure registry and used by a regular SF cluster. It works. Now I need to cover the gap with giving those a try. I imagine I'm not the only one who's looking for a step-by-step guide to deliver NET Framework containers to SF Mesh.

[joergjo]

For the time being, I typically pick one of the (ARM) templates provided in the samples repo and work from there.

[mikkelhegn]

Take a look at this as well to easy get the required deployment artifacts created: https://marketplace.visualstudio.com/items?itemName=mfery.sf-mesh-tools

[abaymar]

This extension requires Visual Studio Code. Is there a version that works with Visual Studio Professional?

I'm asking because, to start with, my containers require .NET Framework and from what I understand it's not something that VS Code fully supports.

[mikkelhegn]

The Service Fabric Mesh SDK preview and VS extension for Mesh, which eventually will also support debugging .net apps in containers. But if all you need is the arm template to deploy, the VSCode extension will give you that.

[abaymar]

@MikkelHegn is there a manual on how to use it?

I have specified sf-mesh-tools.defaultSubscriptionId, sf-mesh-tools.defaultResourceGroup and sf-mesh-tools.defaultTemplateFile values.

Then I typed "Service Fabric Mesh: Create Application" and hit [Enter] in the VS Code command prompt and it said "Command 'Service Fabric Mesh: Create Application' resulted in an error."

[mikkelhegn]

Please check this repo: https://github.com/michaelfery/vscode-sf-mesh-tools @michaelfery (the author) can help.

There are a few pre-reqs you need to install.

[abaymar]

@MikkelHegn, yes, I saw the repo. How do I diagnose the error that I'm given?

[mikkelhegn]

There is one issue opened over there in regards to create application: https://github.com/michaelfery/vscode-sf-mesh-tools/issues/7 If that's not what you see, please open an issue in that repo.

I do remember that you need to have a folder open for that to work. You can try to fall back to the yeoman generator, which the extension relies on: https://github.com/michaelfery/generator-azuresfmesh

[michaelfery]

A PR for adding an explicit error when no workspace is opened has been merged in michaelfery/vscode-sf-mesh-tools#10 Check v0.8 of the extension.