Solved

Error creating a new project in 25R2

Forum|Forum|3 months ago
October 17, 2025
29 replies
466 views

+3

Joe Schmucker
Captain II

I am trying to create a new project in VS on a 25R2 instance. (first time working in 25R2).

I open the project and simply try to compile it. I have not added anything to the project...just the default that was created.

I get this error:

Unable to find package Microsoft.Bcl.AsyncInterfaces. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, TestSDK
I see that there was a similar error a couple of years ago, but it did not address my issue.

From the above link, I tried removing Microsoft.Bcl.AsyncInterfaces from my csproj file. It compiles after doing that. But then the site will not load.

After killing the site, I can get it back up by upgrading the site only using the installation tool.

Note that simply attempting to compile my project in VS, it kills the site.

Could not load file or assembly 'Microsoft.Extensions.Options.ConfigurationExtensions' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I “think” this might have something to do with the TestSDK I installed for 24R2.

I looked under Extensions in Visual Studio, but I don’t see anything custom other than Acuminator.

I tried disabling the Acuminator extension. Still have an error (site is killed).

In the Nuget package manager, it looks like this version is installed in my project:

That dll is not listed in my project references

In all the projects I’ve done prior to 25R2, that dll is listed.

I thought I’d ask here before submitting a support ticket in case it is an easy fix.

Best answer by Vignesh Ponnusamy

Hi All,

We are able to reproduce the issue with customization project extension in 25R2 and have reported it our engineering team. To workaround the issue, you can edit the project .csproj file(using Notepad) to add <Private>False</Private> to all the Acumatica dlls(example below),

    <Reference Include="PX.Common">
      <HintPath>..\..\..\..\Bin\PX.Common.dll</HintPath>
      <Private>False</Private>
    </Reference>
    <Reference Include="PX.Common.Std">
      <HintPath>..\..\..\..\Bin\PX.Common.Std.dll</HintPath>
       <Private>False</Private>
    </Reference>
    <Reference Include="PX.CS.Contracts">
      <HintPath>..\..\..\..\Bin\PX.CS.Contracts.dll</HintPath>
    <Private>False</Private>
    </Reference>
    <Reference Include="PX.Data">
      <HintPath>..\..\..\..\Bin\PX.Data.dll</HintPath>
      <Private>False</Private>
    </Reference>
    <Reference Include="PX.Objects">
      <HintPath>..\..\..\..\Bin\PX.Objects.DLL</HintPath>
       <Private>False</Private>
    </Reference>

After updating the .csproj file, copy the Microsoft.Extensions.Options.ConfigurationExtensions.dll from new/different 25R2 site to the site with the issue. This should allow you to compile the customization project extension without any issues. Hope that helps!

Good Luck,

Show first post

1
2

Forum|pagination.label 2 / 2

+5

Vignesh Ponnusamy
Acumatica Moderator
Answer
Forum|Forum|3 months ago
October 24, 2025

Hi All,

We are able to reproduce the issue with customization project extension in 25R2 and have reported it our engineering team. To workaround the issue, you can edit the project .csproj file(using Notepad) to add <Private>False</Private> to all the Acumatica dlls(example below),

    <Reference Include="PX.Common">
      <HintPath>..\..\..\..\Bin\PX.Common.dll</HintPath>
      <Private>False</Private>
    </Reference>
    <Reference Include="PX.Common.Std">
      <HintPath>..\..\..\..\Bin\PX.Common.Std.dll</HintPath>
       <Private>False</Private>
    </Reference>
    <Reference Include="PX.CS.Contracts">
      <HintPath>..\..\..\..\Bin\PX.CS.Contracts.dll</HintPath>
    <Private>False</Private>
    </Reference>
    <Reference Include="PX.Data">
      <HintPath>..\..\..\..\Bin\PX.Data.dll</HintPath>
      <Private>False</Private>
    </Reference>
    <Reference Include="PX.Objects">
      <HintPath>..\..\..\..\Bin\PX.Objects.DLL</HintPath>
       <Private>False</Private>
    </Reference>

After updating the .csproj file, copy the Microsoft.Extensions.Options.ConfigurationExtensions.dll from new/different 25R2 site to the site with the issue. This should allow you to compile the customization project extension without any issues. Hope that helps!

Good Luck,

#VP

Like

+3

Joe Schmucker
Author
Captain II
Forum|Forum|3 months ago
November 2, 2025

Hi @Vignesh Ponnusamy

I hate to pile on, and maybe I should create a new topic, but I just installed a vanilla 25R2 with sales demo data. I created a new test project. I cannot even add the GL301000 screen to the project.

I tried several approaches:

Out of the box attempt without changing anything

Created a new project Test
Opened GL301000
Inspected the Module element
Clicked Customize
Selected the Test project
Got this error

Changed the GL301000 to Classic. Repeated steps 3 through 5, got this error

Opened the Test project in Project Editor, tried to add the GL301000 screen (Customize Existing Screen), GL301000 is set to use MUI, got this error:

I verified I have Customization rights:

I closed the Test project, re-opened it, and GL301000 is shown in the Screens. I can now open the screen in the editor.

I would find it hard to believe I am the only one with these issues. I am doing this on a brand new laptop.

We just upgraded one of our customers to 25R2. It appears that when you upgrade to 25R2 from a 24 version, this does not happen. Next, I’m going to install a demo 24R2 and upgrade it to 25R2 and see what happens.

My opinion: 25R2 is not ready for prime time.

FYI, I just bought a Dell Pro Max laptop with Intel Core 9 and every upgrade available. It cost over 7K, but it is literally twice as fast to load a site locally after compiling in VS. This is saving me hours per day in development. I highly recommend this laptop.

Joe Schmucker, CPA | Software Engineer | Acumatica ERP Developer

Like

+3

Joe Schmucker
Author
Captain II
Forum|Forum|3 months ago
November 2, 2025

UPDATE.

Installed demo of 24R2. I named it 25R2 since I know I am upgrading the test site to 25R2.

Did the upgrade. No errors of any kind. I can add the screen to the project in classic and MUI.

In summary, upgrading a 24RX to 25R2 does not seem to cause the errors I described in my previous post. If you want to avoid the errors I encountered when installing a new copy of 25R2, I suggest installing 24R2 and upgrading the site. Make sure you name your new site/db as though you are installing 25R2 so you don’t have a bad legacy name for your site/db.

Joe Schmucker, CPA | Software Engineer | Acumatica ERP Developer

Like

+5

Vignesh Ponnusamy
Acumatica Moderator
Forum|Forum|3 months ago
November 4, 2025

Hi @Joe Schmucker,

In a fresh 25R2 instance, I was able reproduce the Error: You have insufficient rights to access the object (LayoutEditorMaint). error but once I referesh the grid, I see the screen being added to the grid.

For this issue, I would recommend you create a dev support request so we could check this further. Thanks,

#VP

Like

1
2

Forum|pagination.label 2 / 2

Could not load file or assembly 'Microsoft.Extensions.Options.ConfigurationExtensions' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded