# From projects to solutions: before and after

> This page compares the former development and deployment model using **projects** with the new unified **solutions** experience in UiPath®. You can check the key differences in design, packaging, deployment, and management across the development lifecycle.

This page compares the former development and deployment model using **projects** with the new unified **solutions** experience in UiPath®. You can check the key differences in design, packaging, deployment, and management across the development lifecycle.

## Design time

In **Studio Web**, any newly created project is automatically part of a **Solution**.

In **Studio Desktop**, developers can open and work on existing solutions and their contained RPA automations, but can still create standalone projects.This page compares the former development and deployment model using projects with the new unified solutions experience in UiPath®. You can check the key differences in design, packaging, deployment, and management across the development lifecycle.

## Packaging

Table 1. Packaging differences

    
        
            Concept
            Build and deploy projects
            Build and deploy solution
        
    
    
        
            Packaging (produced by the Publish button in Studio Web)
            Produces a <code>nupkg</code> file containing one project.
            Produces a <code>.zip</code> Solution Package containing multiple projects, their resource definitions, and deployment configuration.
        
        
            Deployment
            
                You create a project from a package using the Add Process button in Orchestrator.
                
            
            
                You deploy a solution from a solution package via Tenant &gt; Solutions &gt; Packages.
                
            
        
        
            Folders
            
                Processes are added to folders.
                
            
            
                Solutions are deployed to solution folders, and all resources from that solution are automatically included.
                
            
        
        
            Package Requirement Resolution (Bindings)
            
                Performed from the Package Requirements tab in Orchestrator.
                
            
            
                For the moment, this can only be done via the Package Requirements tab in Orchestrator.
                
            
        
    

## Publishing and deployment

 <caption>
  Table 2. Publishing and deployment differences
 </caption>
 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
    Deployed packages in Orchestrator 
    Deployed solutions in Orchestrator 
  
 
 
  
    Project logs, jobs, requirements, and upgrades are managed from the folder where the project is deployed. 
    Upgrades are handled from the Solutions tab. Project logs, jobs, and requirements continue to be accessible from the Solution Folder. 
  
  
    How to upgrade a project:  Go to the project folder.  Navigate to the Automations tab.  Go to the Processes tab.  Choose the project you want to upgrade and select the Upgrade icon.  Alternatively, you can select the More Actions button and choose Upgrade to latest version from the dropdown.   
    How to upgrade a project:  Go to the Tenant page.  Navigate to the Solutions tab.  Go to the Deployments tab.  Choose the solution you want to upgrade and select the More Actions icon.  Choose Upgrade / Downgrade from the dropdown.   
  
  
    How to view project logs or jobs:  Go to the project folder.  Navigate to the Automations tab.  Go to the Jobs tab to view project jobs.  Go to the Logs tab to view project logs.  
    How to view project logs or jobs:  Go to the solutions folder.  Navigate to the Automations tab.  Go to the Jobs tab to view project jobs.  Go to the Logs tab to view project logs.