I cannot successfully compile an extension library that is freshly created using the Customization Project -> Extension Library -> Create New.
When compiling the freshly created extension library, I get the following error in the output, but no errors show in the error report:
1>C:\Program Files (x86)\Acumatica ERP\SilcotekDev\App_Data\Projects\ManufacturingTest\ManufacturingTest\Test.cs(6,7,6,9): error CS0246: The type or namespace name 'PX' could not be found (are you missing a using directive or an assembly reference?)
I have another custom extension library which had compiled successfully in the past, but today is not. Here is the full error list from that project's compilation:
I do have a custom DAC which I imported directly into the extension library, and I had compiled it before with that DAC added. Today it won't compile at all.
With update 3 of version 6.1 Acumatica has changed the target framework for its websites from 4.5.1 to 4.5.2. Unfortunately, the target version of the Addon.csproj VS project from the \App_Data\WebsiteSolution\Addon folder was not updated to .Net Framework 4.5.2 until update 9 of ver. 6.1 (build #6.10.0945). Because of the lower target version set for extension library VS project, VS cannot build the dll and therefore copy it to the Bin folder of your website.
There are 2 ways to resolve this type of an issue:
Change target framework version in VS for your extension library project:
Open the Addon.csproj VS project in a text editor, like NotePad, and change the target framework to v4.5.2 as shown in the screenshot below (located in the \App_Data\WebsiteSolution\Addon folder inside your Acumatica website root folder). Create a new customization project inside Acumatica, then in Customization Manager create extension library for the new project
There are a lot of things that could cause this problem.
1. is your program set up to read the PX namespace?
2. are you References setup the right way. You can always check by right clicking on the reference and selecting "Add reference"
Related
I'm creating a aar from my library project. But if I add it in another project its treated as "unspecified". (name="MyLibrary-unspecified") If I click the .aar its also saying "unknown (version unknown)". How to set up this properly? (I name the file MyLibrary-1.1.0.aar but this does not help)
Everytime I try to create a bridge.net new project I get the following error:
Could not add all required packages to the project. The following
packages failed to install from [the user appdata local
folder]\Microsoft\VisualStudio\14\extensions\IJHDC25V.XOU\Packages.
Bridge.1.10.0 : Solution is not opened or not saved. Please ensure you
have an open and saved solution.
Trying to build the project leads to the 'Bridge' namespace missing.
I did the following:
Download the bridge.net .vsix package from
https://visualstudiogallery.msdn.microsoft.com/dca5c80f-a0df-4944-8343-9c905db84757
Run the package
Create a new project -> Bridge.net -> Class Library
Named the project 'Demo'
I verified the folder exists and is populated. I've tried running Visual studio as an administrator and as a standard user.
How do I get a working blank Bridge.net project with the visual studio template?
I realise that this doesn't quite answer precisely the question asked but I don't use the VSIX package to create Bridge.NET projects, I just create a new (standard) class library and then use NuGet to add "Bridge". This adds the Bridge compiler and it adds a "demo.html" file and a basic "bridge.json" config file to get you started. (If you wanted to write a Bridge library and you didn't want the "starter park" items then you can add the NuGet package "Bridge.Min" instead).
The project needs to be saved to disk.
In Visual Studio under Tools / Options / Projects and Solutions tick the Save new projects when created checkbox.
Then create a new project.
I have a Windows application on C# and some console application.
In that solution I have two libraries named A and B.
Library A is using reference of Library B.
But when I built my application I got the error below:-
Cannot register assembly "A.dll". Could not load file or assembly
"B.dll" or one of its dependencies. The specified module could not be found.
Do you have a circular reference? Check your library B does not hold a reference to A.
If that isn't the case, right click on your solution name.
Select 'Project Dependencies';
Select Project A and tick project B to set it as the dependency.
See the other tab 'Build Order' and make sure Project B is above project A.
If this doesn't solve your problem, Go to each project properties;
Set 'Target Framework' in Application pane and 'Platform Target' in Build pane are same for those projects.
For the win console application copy all .dll to location .exe and then test to run from
window command (cmd), after run you still get the same previous error "Cannot register assembly A.dll. Could not load file or assembly B.dll" I think the .dll was build under
Dot net framework you are using on project. Example sometime you cannot reference .dll Dot net 2.0 with the project Dot net framework 4.0
Aey.Sakon
I'm trying to create simple DataAccess portable class library for 3 platforms (ios, android, wp7.5).
All I want is to create webrequests, convert data and return it to UI of each platform.
I was able to create library like this (portable) under Mac OS X Xamarin Studio and successfully used it at iPhone app.
But then I opened this solution under Visual Studio (to add Windows Phone UI project) it gave me build error with description that it couldn't find System.Net namespace.
When I checked portable class targets I was surprised to see there even XBOX selected:
When I selected correct targets (MonoDroid/Monotouch/WindowsPhone7.5) I was able to compile but when I start the app I received the following error:
"c:\Downloads\Noname.CrossXam\Noname.CrossXam\Noname.CrossXam.iPhone\Noname.CrossXam.iPhone.csproj"
(_RemoteBuild target) (1) -> (_ResolveAssemblies target) ->
C:\Program Files
(x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(68,3):
error : Exception while loading assemblies:
System.IO.FileNotFoundException: Could not load assembly 'System.Net,
Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e'.
Perhaps it doesn't exist in the MonoTouch profile? ...
0 Warning(s)
1 Error(s)
Same code (same solution) works just fine under Mac OS X with Xamarin Studio.
Sample solution is here:
https://dl.dropboxusercontent.com/u/19503836/Noname.CrossXam.zip
Please advise.
The issue was in System.Net.dll assembly which is not exists under MonoTouch & MonoAndroid profiles. But that classes are implemented at System.dll under those profile and to make it work you need TypeForwardedToAttribute.
All that type forwarding configuration exists at MVVMCross nuget package which I was able to install only after updating nuget (the last comment from this post: http://slodge.blogspot.com/2013/04/my-current-pcl-setup-in-visual-studio.html)
So there were two issues:
1. Old nuget package manager (update is required)
2. TypeForwardedToAttribute configuration (exists at MvvmCross)
Hope it will be useful for someone.
Have you tried to change target framework to .Net 4.5? You should see Profile104 in your .csproj file
I am moving a VB.net class from a project using .net 2.0 to a project using .net 4.5
In the class is a Imports System.Web.UI.Design, however, in the 4.5 project this statement shows up with a green squiggly line under it and the mouseover text says: "Namespace or type specified in the Imports 'System.Web.UI.Design' doesn't contain any public members or cannot be found."
I have added the System.Design.dll as a reference to the project and in the Object Browser, I can see the System.Web.UI.Design namespace. I have verified that the system.design.dll exists in Windows/Microsoft.Net/Framework/v4.0.30319 and Program Files (x86)/Reference Assemblies/Microsoft/Framework/.NETFramework/v4.5 directories.
I am using Visual Studio 2012.
In Windows/Assembly, I only see the 2.0.0.0 version of the assembly, however, Add Reference in VS shows the version I added as 4.0.0.0. Tried dropping the dll from the v4.0.30319 directory into windows/assembly and using the gacutil. While gacutil said the assembly was added, it still didn't appear in Windows/Assembly.