Hi Marcio,

Yes, the blog post you found is slightly out of date in that the namespaces and some classes have changed since it was written.

as of v8 you can do the following (assuming you have a class with the NPoco table/column settings as you want it)

Create a migration class

    public class MigrationCreateTables : MigrationBase
    {
        public MigrationCreateTables(IMigrationContext context) 
            : base(context)
        { }

        public override void Migrate()
        {
            if (!TableExists("myTable"))
                Create.Table<MyNPocoTableClass>().Do();
        }
    }

Create a migration plan

public class MyMigrationPlan : MigrationPlan
{
    public TranslationMigrationPlan() 
        : base("MyApplicationName")
    {
        From(string.Empty)
            .To<MigrationCreateTables>("first-migration");
    }
}

Have a component to start the migration plan (this is where UmbracoUserComponent has gone!)

public class MyCustomComponent: IComponent
{
    private readonly IScopeProvider scopeProvider;
    private readonly IMigrationBuilder migrationBuilder;
    private readonly IKeyValueService keyValueService;
    private readonly ILogger logger;

    public MyCustomComponent(
        IScopeProvider scopeProvider, 
        IMigrationBuilder migrationBuilder, 
        IKeyValueService keyValueService, 
        ILogger logger)
    {
        this.scopeProvider = scopeProvider;
        this.migrationBuilder = migrationBuilder;
        this.keyValueService = keyValueService;
        this.logger = logger;
    }

    public void Initialize()
    {
        // perform any upgrades (as needed)
        var upgrader = new Upgrader(new MyMigrationPlan());
        upgrader.Execute(scopeProvider, migrationBuilder, keyValueService, logger);

    }

Register the component in the compositions (so that it is called by Umbraco)

    public class MyAppComposer: IUserComposer
    {
        public void Compose(Composition composition)
        {
            // component for startup
            composition.Components()
                .Append<MyCustomComponent>();
        }
    }

thank you very much Kevin.

now I understand how it works. I did not know I could use a constructor MyCustomComponent like that.

What about ApplicationContext.Current.DatabaseContext.Database, do you know how to access the Umbracodatabase instance? is actually using the practice of the sample code I showed:

using (var scope = Current.ScopeProvider.CreateScope())
{
    var sql = scope.SqlContext.Sql()
        .Select<Record>(x=>x.Form)
        .From<Record>()
        .Where<Record>(x => x.UniqueId == recordId);

    var formId = scope.Database.ExecuteScalar<Guid>(sql);

    scope.Complete();

    return GetForm(formId);
}

great!! thank you Kevin

Hi Marcio

Sorry to jump onto your forum post, but I am working on migrating the Tag Manager package to V8.

I have one last issue to solve and I will be able to build the package and see if it works (fingers crossed).

My issue relates to IScopeProvider - in terms of your code are you able to show me your code where you call MyService.GetList(12345) ?

What I am trying to understand is how to instantiate a new Scope provider to pass to the constructor of MyService.

Hope this makes sense.

Cheers

Nigel

is working on a reply...