I install designer tools modules on orchard 1.7 . but after installation it give me the following Error :
1. Install any dependent module.
2. Remove the assembly reference from the project file if it's not needed.
3. Ensure the assembly reference is present in the 'bin' directory of the module.
4. Ensure the assembly reference is present in the 'bin' directory of the application.
5. Specify the strong name of the assembly (name, version, culture, publickey) if the assembly is present in the GAC.
not I need help how to resolve this problem .
or learn me how can I remove this modules from the command line ?
what's that I must enter in orchard command line to remove this modules ?
thanks
Regards :
Raha
You probably installed the wrong version of the module. You actually didn't have to install anything as it comes standard with Orchard. Delete Modules/Orchard.DesignerTools and copy it back from the original distribution of Orchard that you used.
Related
I inherited an old web application built using IIS, and I'm trying to figure out how to build it. I'm running into this Build (web): Object reference not set to an instance of an object. error during build time. Aren't null object references supposed to be runtime errors, not compile errors? Can anyone explain to me what's happening here and how to fix it?
Have you downloaded the packages your projects reference? And do the assemblies in your bin folder match up with your web.config (check version numbers too)?
Edit: If the packages in the bin folder don't match, you can redownload them with NUGET -
note which packages are out of sync - grab their id values from the package nodes in the web.config
Inside your VS solution, check each project's references to see where the missing packages are referenced
Inside your VS solution, go to: Tools > NuGet Package Manager > Package Manager Console
for each missing package run the following command in the Package Manager Console:
Update-Package -Id <package_name> –reinstall
where <package_name> == the id value you captured from the web.config at step 1.
I created a small executable that is used to run and debug specific libraries from other solutions. The executable is given the path to a library as a command line argument which the executable loads at runtime.
I want to put my executable in a Nuget package, and have consuming libraries just add the Nuget package to be able to run and debug, using a launchSettings.json.
Because the executable is in the tools/ directory of the Nuget package, its path is put into the PATH environment variable by the Package Manger Console. Therefore the launchSettings can simply just call the executable.
I create my Nuget package with nuget.exe pack my.nuspec -Version 1.0.0, with my.nuspec containing:
<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
<metadata>
<id>DebugHost</id>
<version>$version$</version>
<title>DebugHost</title>
<authors>Some company</authors>
<owners>Some company</owners>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<description>DebugHost</description>
<summary>DebugHost</summary>
<copyright>2020, Some company</copyright>
</metadata>
<files>
<file src="bin\Debug\netcoreapp3.1\*" target="tools" />
</files>
</package>
From consuming library projects I put in Properties\launchSettings.json containting:
{
"profiles": {
"DebugHost": {
"commandName": "Executable",
"executablePath": "my.exe",
"commandLineArgs": "$(ProjectDir)$(OutDir)$(TargetName)$(TargetExt)"
}
}
}
I have three different questions that are somewhat related, as any might answer another:
This setup only works as long as I keep the Package Manager Console opened. If I try to Debug / Launch the library without first opening the Package Manager Console, the launch fails because it cannot find the executable. Unable to start program 'my.exe'. The system cannot fint the file specified.
Can I for example add a targets file in the Nuget package that will hint its path during build/launch, which in turn I can use as a variable in the launchSettings.json? (If so, how?)
This setup requires that a Properties\launchSettings.json is used in the consuming project. Can I make my Nuget package create that file?
Can the file be an asset in the Nuget that gets copied to the correct place?
Or can I even have an install.ps1 script that creates the json, with the correct absolute path to the executable in it? This would make question 1 answered as well.
The above situation only works with nuget.exe pack and a .nuspec.
Can I instead move stuff into my (new style) .csproj and get this to work with just dotnet.exe pack and the .csproj? (or msbuild.exe -t:pack and the .csproj?) So ultimately I can also just create the package by simply right clicking the project in Visual Studio and selecting Pack from the context menu?
When using dotnet core 2.0-preview1 in vs2017. I got an error about project reference.
I hava a solution with two projects.
This is Common.Bll Project
The Common.Web referenced the project Common.Bll. But the ide told me cannot find Common.Bll with error Using directive is not required by the code and can be safely removed. Cannot resolve symbol 'Bll'
This is Common.Web project
Common.Bll.csproj
Common.Web.csproj
But it can be build succeed and run normally.
Have any way to solve this?
update:
It's working follow the #Svek to change the Common.Bll from netstandard2.0 to netcoreapp2.0.
Your csproj file
Visual Studio doesn't like to behave quite right when the TargetFramework does not totally match up.
Common.Bll.csproj
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
Common.Web.csproj
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
</PropertyGroup>
Make both of them the same, and you should be good to go.
the error:
cannot resolve symbol '< >'
The simple solution is to reinstall all your packages, and make sure all your dependencies are properly showing up in Visual Studio under each project. (Dependencies --> Projects | or | Dependencies --> Assemblies).
In Package Manager
Update-Package -reinstall
More details can be found here to reinstall your packages.
Reference to an unused library
- Update: You can ignore this. Your updated question makes this section no longer apply. -
Until you are actually using a library, Visual Studio will inform you that the referenced library is not required.
using directive is not required by the code and can be safely removed.
You can do one of two things:
1.) Use the library that you are referencing
In your case:
var obj = new Common.Bll.<Your Class>;
2.) Remove library that you are referencing
This can be done quickly by right-clicking and selecting Remove Unused Usings.
The alternative is to use the keyboard shortcut Ctrl+R, Ctrl+G.
i'm trying to use existing project as a library in android studio, it was easy in eclipse. i've imported the project into android studio and every thing works fine but when i try to use is as a library its says "Error:Configuration with name 'default' not found."
i've included the the project in a directory named librairies and i'ave included in setting.gradle
include ':app'
include ':libraries:droidar1'
and i have changed the library into com.android.libray
and added the model in dependecy but its no use
This error means it's looking for a module at a given path, in this case two paths app and libraries/droidar1 and is not finding a buildable module at one or more of them. Make sure there is a build.gradle file at each of those paths with an apply plugin that will tell the build system what plugin to use to build the module.
After adding SFML.NET through Nuget Packge manager I got the following error:
Error 4 The "UnzipNuspec" task was not found. Check the following: 1.) The name of the
task in the project file is the same as the name of the task class. 2.) The task class is
"public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is
correctly declared with <UsingTask> in the project file, or in the *.tasks files located
in the "C:\Windows\Microsoft.NET\Framework\v4.0.30319" directory.
I'm using Visual Studio 2012.
As pointed out in other similar questions, I've tried to close and open MSVS, it didn't helped.
I also checked out the build tools path in the registry, and it points to right directory.
I tried to install and uninstall Nuget packeage.
I found out that error possibly somehow connected to it's dependency : Baseclass.Contrib.Nuget.Output, but I can't find out how to fix it.
It's a bug in their build script.
Go to the packages folder for your solution and locate the following file:
Baseclass.Contrib.Nuget.Output.1.0.6\build\net40\Baseclass.Contrib.Nuget.Output.targets
Around line 84 in that file you'll find a couple of <Using Namespace=... /> tags. Add this after those, before the <Code...> tag:
<Using Namespace="System.Threading" />
I've reported this on their github issues list as well.