One Web Based project have class library,means dll file generate at back end while build my created project
Tried solution 1:
I copied that Dll into "C:\Windows\assembly" folder and register through
"regasm.exe C:\DLLName.dll /tlb:TLBName.tlb"
it's register successfully but,Update site takes too many times, suppose I register dll today then I can find my changes tomorrow
Tried solution 2:
I copied that Dll file and paste in to my server's C:\Windows\System32 folder and register through gacutil -i command from CMD
but it's not worked for me,means can't see changes in site
Tricks is uninstall Dll by regasm /u command and again register it find updated version
But Register DLL not find In C:/Windows/Assembly folder why? I don't know..
Related
I am getting an error of "Could not load file or assembly 'Microsoft.AI.Web' or one of its dependencies" in the browser of my asp.net app. Microsoft.AI.Web is from Microsoft.ApplicationInsights.Web NuGet package.
I noticed this:
LOG: Appbase = file:///D:/Source/Workspaces/AppName/Branches/Main/Application/WT/
LOG: Initial PrivatePath = D:\Source\Workspaces\AppName\Branches\Main\Application\WT\bin
the dll in question is located at D:\Source\Workspaces\AppName\Branches\Main\Application\packages\Microsoft.ApplicationInsights.Web.2.4.1\lib\net45\Microsoft.AI.Web.dll
As for personal dll's -- In the project-->properties-->build-->output path--> I have it set as "..\Any\Debug\". When I build the project the DLL's populate there.
I checked References and code in .csproj file and all the dll are located where I specified to.
I am not sure why it's trying to look at the bin file of the project when I told the output is somewhere else AND to look for the dlls in that same folder(through references and .csproj file). How do I make it so that VS will look for the dlls in the folder path I want instead of "WT\bin"?
When I change my project output path to "bin", it can detect the dll's there EVEN though the path of the dll remains the same( D:\Source\Workspaces\AppName\Branches\Main\Application\packages\Microsoft.ApplicationInsights.Web.2.4.1\lib\net45\Microsoft.AI.Web.dll).
Since it's a Microsoft strong signed DLL, add it to the server's GAC.
If you place it in the GAC, it'll find the file automatically. Another plus there is that if you need it for another project deployed on the same server, you don't need to deploy it again.
Here's some information on how to install a DLL into the GAC on the server machine, assuming gacutil is not installed there. Look at the accepted answer, not the question.
Drag and drop a DLL to the GAC ("assembly") in windows server 2008 .net 4.0
Copy gacutil.exe and gacutil.exe config from your machine to the server's C:\Windows\Microsoft.NET\Framework\v4.0.30319
Then run on the server:
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\gacutil.exe" /i "PATH TO YOUR DLL"
sometimes when I rename the path to a qt project, it cannot be run even though I clean qmake and rebuild it!!! the path does not contain any space. and the project is completely correct and I know that the error is for path renaming , for example when I rename :
D:/abd/projects/LAND_2/Land_QT/...
to
D:/abd/projects/LAND_2/Land2_QT_SA/...
it cannot be build and says that some include file is missing(but the file is there!).
what is the problem?
I work with dynamic qt5.2 on windows 7.
Edit:
when I copy the project folder to a new directory( a path upper than current path) then the project can be build and run.
When you rename the path to the project, go to the project folder and delete the file with .pro.user extension. Open the project and Qt will ask you to configure the project. Choose the required kit, build and run the project.It should build successfully now
If you have changed path multiple times the .pro.user file is created multiple times delete all files with this extension and compile
I am trying to publish an ASP.NET web site project using the Publish Web Site tool but get this error:
ASPNETCOMPILER(0,0): Error ASPRUNTIME: The specified path, file name,
or both are too long. The fully qualified file name must be less than
260 characters, and the directory name must be less than 248
characters.
I see that it is trying to copy the files to a very long path in AppData:
Copying all files to temporary location below for package/publish:
C:\Users\imx0\AppData\Local\Temp\1\WebSitePublish\BMW.Web-424993535\obj\Debug\AspnetCompileMerge\Source.
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v /BMW.Web -p C:\Users\imx0\AppData\Local\Temp\1\WebSitePublish\BMW.Web-424993535\obj\Debug\AspnetCompileMerge\Source C:\Users\imx0\AppData\Local\Temp\1\WebSitePublish\BMW.Web-424993535\obj\Debug\AspnetCompileMerge\TempBuildDir
I couldn't find anything about this temp directory in my .pubxml publish profile. How can I change the temporary directory that Visual Studio copies the files to?
Add this to your publish profile to modify the temporary directory for package/publish:
<AspnetCompileMergeIntermediateOutputPath>c:\shortPath\</AspnetCompileMergeIntermediateOutputPath>
Go to your web project folder, navigate to Properties\PublishProfiles folder.
open your profile file profile_name.pubxml (not the profile_name.pubxml.user)
copy/past <AspnetCompileMergeIntermediateOutputPath>c:\shortPath\</AspnetCompileMergeIntermediateOutputPath> under the <PropertyGroup> tag
save your file, you would be able to publish your website using this profil
This is sort of an aside answer, but I ran into this problem when trying to MSBuild a solution that depended on nodeJS and gulp. The problem was that the gulp dependency tree became very deep and the aspnet_compiler was trying to copy that tree to a deeper directory, resulting in this error. I tried everything noted in here but nothing worked.
As it so happened, I was building with TFS, so my solution was to run an attrib +h node_modules\* /S /D before msbuild to hide the directory tree and then attrib +h node_modules\* /S /D. That did it for me.
Sure would be nice if the error thrown in this situation by the compiler revealed the path that caused the write to fail...
try adding this
<IntermediateOutputPath>..\Temp</IntermediateOutputPath>
to the default <propertyGroup />
None of the other answers worked for me.
Visual Studio 2013 Community Edition.
I changed the TMP and TEMP environment variable to a short folder name and it worked.
We identified the lengthy files/folders using this solution, then corrected the issue from there:
Run this script at the command prompt: dir /s /b | sort /r /+261 > out.txt it will output all file paths into the out.txt file
Copy the output to an Excel file
In the next column over from what you pasted in add this Excel function: =LEN(A1) where "A1" is the cell, copy this against every file length so you can see how long the paths are
Sort in Excel by the path length
Identify the lengths over the recommended limit
I know this is a bit long-winded but if you have several files that are resulting in this issue you'll be able to see them all.
Even though the content of node_modules was not included in neither version control not in the *.csprojfile itself Deleting the whole node_modules folder did the trick for me.
You can try the selected solution for correcting the long file path issue.
Still if not able to publish due to some other issue, You can try below method.
=> If the 'Solution Configuration' is in 'Debug' mode, please change the same to 'Release' mode and Publish the files.
=> If the Solution Configuration is in Release mode, and if the problem still persists, please try to delete the dll generated earlier in the 'Release' folder of our project and Publish the project once again.
Any of the above method will solve the issue.
For me, using Visual Studio 2019, the only change to the publish profile .pubxml file that worked was:
<WPPAllFilesInSingleFolder>c:\shortPath\</WPPAllFilesInSingleFolder>
I discovered this property at line 484 of Microsoft.Web.Publishing.targets file. Full path was C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\Web.
unable to update auto-refresh reference 'ajaxcontroltoolkit.dll and
commonlogging.dll
I am getting this warning every time I build the project but the project is running fine without breaks in local system but I am getting error page in godaddy after uploading to server. is this the reason for 500 error in godaddy shared hosting server?
I had this same problem with the AjaxControlToolkit. I've got no idea what caused it, but by simply re-installing the toolkit into my project with NuGet, that fixed it.
Install the package by following the steps below:
Right-click on your project and select Manage NuGet Packages.
Search the online repository for the package you want. In my case, this was 'ajaxcontroltoolkit'.
Find the package in the list of results that appears and click the Install button on it.
What this does is it removes all previous references of the package (older DLLs and references in your web.config file) and replaces them with newer, correct references
It's that simple.
Hope this helps you
Look in the bin folder of the project - for a file called - in your case:
ajaxcontroltoolkit.dll.refresh
This will have an incorrect path to the dll file. You need to update the path to wherever the dll is now.
Had this same issue and manually creating a .refresh file for its DLL helped. Once I figured the origin of the relative path is the solution folder, and put that in the .refresh, everything worked for this and other references.
I hope this helps somebody...
Im using VS2017 and had an ASP project with 28 Warnings:
Unable to update auto-refresh reference 'XXXXX.dll'. Cannot find
assembly 'F:\Program Files (x86)\Microsoft Web Tools\Packages\…
...well...that directory had been removed!
To make matters worse (or better) when I create a new ASP project the references are handled a little different in solution explorer...and the assemblies referenced in the new project are in C:\Program Files (x86)\Microsoft Visual Studio\Shared
To fix my warnings...I edited the .refresh file.
You can do this by: 1: Double clicking the warning. 2: Navigate to it
in solution explorer under the Bin folder.
And changed (example)
..\..\..\..\..\..\..\Program Files (x86)\Microsoft Web Tools\Packages\AspNet.ScriptManager.bootstrap.3.0.0\lib\net45\AspNet.ScriptManager.bootstrap.dll
to
C:\Program Files (x86)\Microsoft Visual Studio\Shared\Packages\AspNet.ScriptManager.bootstrap.3.0.0\lib\net45\AspNet.ScriptManager.bootstrap.dll
I had the same issue / what solved it for me was simply to do a "Refresh folder" on the Bin folder.
I'm trying to host a website i'm getting an error regarding assemblies.I have added the assemblies to the bin folder also.Fllowing is the error page
http://d3430264.u711.laknetwork.com/real/login.aspx
I believe this is a version related issue. You may have dropped a dll into bin but it's version does not match with the expected one.
You can edit the AssemblyInfo.cs to have the version tag as this [assembly: AssemblyVersion("1.0.0.0")] . And then clean the solution and redeploy
Do one thing, before publishing, select the reference and open its properties window. See if there you have option copy to local. It sounds the assembly resides in GAC and is not available while deployment. Or you can copy paste the same version assmbly in target machine in System32 directory or local bin and register using regasm /tlb (managed dll) , regsvr32 (unmanaged).