Skip to main content

Featured post

XM Cloud content sync from prod to uat or UAT to prod step by step

When working with Sitecore, it’s common to need content synchronization across environments. Today, I’ll walk you through the steps to sync content from Production to UAT/TEST and vice versa. Steps to Follow 1. Set Up Your Workspace Create a folder on your computer where you will manage the script files and exported data. Open the folder path in PowerShell to begin scripting. We need to run some scripts in PowerShell to update the folder with the basic requirements for syncing content. PS C:\Soft\ContentSync> dotnet new tool-manifest PS C:\Soft\ContentSync> dotnet nuget add source -n Sitecore https://nuget.sitecore.com/resources/v3/index.json PS C:\Soft\ContentSync> dotnet tool install Sitecore.CLI PS C:\Soft\ContentSync> dotnet sitecore cloud login If the above error occurs, you will need to run a different command to resolve the issue. PS C:\Soft\ContentSync> dotnet sitecore init now, Again run above command to open and authenticate with XM Cloud. It will be there a...

CRUD operation using MongoDB with asp.net mvc project


Insert, Delete and Update using MongoDB with ap.net mvc project.

In this article i am going to explain with example for user registration and login step by step.

Open your Visual Studio and create a project.

Add MongoDB driver in your project by using the following process.

Go to Tools > Library Package Manage > Manage Nugget manager for sultion.

It will open new window , search online MongoDB and install it in your project.

Now create a class in Model folder of project . Here , I have created User Class and added some properties.


using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using MongoDB.Bson.Serialization.Attributes;

namespace M101DotNet.WebApp.Models
{
    public class User
    {

        [BsonRepresentation(MongoDB.Bson.BsonType.ObjectId)]
        public string Id { get; set; }

        public string Name { get; set; }

        public string Email { get; set; }
          }
}

Now adding another class in this project which can connect with MongoDB

Here, I have created mongodbcontext  class to perform operation with MongoDB.

          using System;
using System.Collections.Generic;
using System.Configuration;
using System.Linq;
using System.Web;
using MongoDB.Driver;

namespace M101DotNet.WebApp.Models
{
    public class BlogContext
    {
        public const string CONNECTION_STRING_NAME = "Blog";
        public const string DATABASE_NAME = "blog";
        public const string POSTS_COLLECTION_NAME = "posts";
        public const string USERS_COLLECTION_NAME = "users";

        private static readonly IMongoClient _client;
        private static readonly IMongoDatabase _database;

        static BlogContext()
        {
            var connectionString = ConfigurationManager.ConnectionStrings[CONNECTION_STRING_NAME].ConnectionString;
            _client = new MongoClient(connectionString);
            _database = _client.GetDatabase(DATABASE_NAME);
        }

        public IMongoClient Client
        {
            get { return _client; }
        }

        public IMongoCollection<User> Users
        {
            get { return _database.GetCollection<User>(USERS_COLLECTION_NAME); }
        }
    }
}

and finally, I have created AccountController in project please see below code which help you more understand  .

using System;
using System.Collections.Generic;
using System.Linq;
using System.Security.Claims;
using System.Threading.Tasks;
using System.Web;
using System.Web.Mvc;
using MongoDB.Driver;
using M101DotNet.WebApp.Models;
using M101DotNet.WebApp.Models.Account;

namespace M101DotNet.WebApp.Controllers
{
    [AllowAnonymous]
    public class AccountController : Controller
    {
        [HttpGet]
        public ActionResult Login(string returnUrl)
        {
            var model = new LoginModel
            {
                ReturnUrl = returnUrl
            };

            return View(model);
        }

        [HttpPost]
        public async Task<ActionResult> Login(LoginModel model)
        {
            if (!ModelState.IsValid)
            {
                return View(model);
            }

            var blogContext = new BlogContext();
            // XXX WORK HERE
            var user = await blogContext.Users.Find(x => x.Email == model.Email).SingleOrDefaultAsync();
            // fetch a user by the email in model.Email

            if (user == null)
            {
                ModelState.AddModelError("Email", "Email address has not been registered.");
                return View(model);
            }

            var identity = new ClaimsIdentity(new[]
                {
                    new Claim(ClaimTypes.Name, user.Name),
                    new Claim(ClaimTypes.Email, user.Email)
                },
                "ApplicationCookie");

            var context = Request.GetOwinContext();
            var authManager = context.Authentication;

            authManager.SignIn(identity);

            return Redirect(GetRedirectUrl(model.ReturnUrl));
        }

        [HttpPost]
        public ActionResult Logout()
        {
            var context = Request.GetOwinContext();
            var authManager = context.Authentication;

            authManager.SignOut("ApplicationCookie");
            return RedirectToAction("Index", "Home");
        }

        [HttpGet]
        public ActionResult Register()
        {
            return View(new RegisterModel());
        }

        [HttpPost]
        public async Task<ActionResult> Register(RegisterModel model)
        {
            if (!ModelState.IsValid)
            {
                return View(model);
            }

            var blogContext = new BlogContext();
          
            var user = new User
            {
                Name = model.Name,
                Email = model.Email
            };
            await blogContext.Users.InsertOneAsync(user);
            // create a new user and insert it into the database

            return RedirectToAction("Index", "Home");
        }

        private string GetRedirectUrl(string returnUrl)
        {
            if (string.IsNullOrEmpty(returnUrl) || !Url.IsLocalUrl(returnUrl))
            {
                return Url.Action("index", "home");
            }

            return returnUrl;
        }
    }
}





Comments

Popular posts from this blog

What is layout service in sitecore and how to configure it

 What is layout service in sitecore and how to configure it The Layout Service in Sitecore is a RESTful API that provides access to the data and presentation details of a Sitecore website, allowing developers to build modern, headless applications that consume content from Sitecore. To configure the Layout Service, you need to perform the following steps: Install the Sitecore JavaScript Services (JSS) package on your Sitecore instance. Define a new route in the jss.config file to specify the endpoint for the Layout Service. Configure the security settings to specify the roles and users who are allowed to access the Layout Service. Test the Layout Service endpoint to ensure that it is configured correctly and returning data as expected. Note that these steps are just a high-level overview and the specific details of each step may vary depending on the version of Sitecore you are using and the specific requirements of your project.

HttpRequestProcessed pipeline implementation in sitecore with C# code

 HttpRequestProcessed pipeline implementation in sitecore with C# code Here is an example of how you can implement the HttpRequestProcessed pipeline in Sitecore using C# code: using System; using Sitecore.Pipelines.HttpRequest; namespace MySite.Pipelines {     public class MyHttpRequestProcessed : HttpRequestProcessor     {         public override void Process(HttpRequestArgs args)         {             // Perform custom processing logic here             Console.WriteLine("HttpRequestProcessed pipeline processed successfully");         }     } } This code defines a custom HttpRequestProcessed processor that will be executed as part of the HttpRequestProcessed pipeline. The Process method is called when the pipeline is executed, and you can perform any custom processing logic you need within this method. To activate this custom process...