GordonLiq
asked on
asp.net deploy error , dll exists in both xxx and yyy
Hi ,
I keep get this error message when I simply overwrite all the dlls when do the upgrade.
the error message like this
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0433: The type 'ASP.modules_residents_res identbase_ ascx' exists in both 'c:\Windows\Microsoft.NET\ Framework6 4\v4.0.303 19\Tempora ry ASP.NET Files\root\584cdf26\30bd83 dd\App_Web _lyly2owi. dll' and 'c:\Windows\Microsoft.NET\ Framework6 4\v4.0.303 19\Tempora ry ASP.NET Files\root\584cdf26\30bd83 dd\App_Web _residentb ase.ascx.8 60c942b.-q descom.dll '
and to fix the problem , I need to stop the website, delete all files under
c:\Windows\Microsoft.NET\F ramework64 \v4.0.3031 9\Temporar y ASP.NET Files\root\584cdf26
and start the website again .
any idea why this keep happen? I dont want to delete the temp file each time I do the website as the website needs to upgrade very frequently.
I keep get this error message when I simply overwrite all the dlls when do the upgrade.
the error message like this
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0433: The type 'ASP.modules_residents_res
and to fix the problem , I need to stop the website, delete all files under
c:\Windows\Microsoft.NET\F
and start the website again .
any idea why this keep happen? I dont want to delete the temp file each time I do the website as the website needs to upgrade very frequently.
ASKER
Hi ,
thank you for reply , my problem is different to that link , as my project running well after I delete the temp file and start the IIS again , and I think his project not running at all.
also , he get 2 dll with random name , but I only get one , the strange is I get another dll just for a single .ascx file
App_Web_residentbase.ascx. 860c942b.- qdescom.dl l
this dll looks not for project , it is only for a residentbase.ascx file.
I have checked and there is not special code for that file
thank you for reply , my problem is different to that link , as my project running well after I delete the temp file and start the IIS again , and I think his project not running at all.
also , he get 2 dll with random name , but I only get one , the strange is I get another dll just for a single .ascx file
App_Web_residentbase.ascx.
this dll looks not for project , it is only for a residentbase.ascx file.
I have checked and there is not special code for that file
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
I think the Scenario 3 refer to my issue , but the solution is what I want to avoid ,
I dont want to clear the temp folder every time I deploy the website, what I current do is just copy all file to IIS folder and overwrite it.
Description: By default, when an ASP.NET Web application is compiled the compiled code is placed in the Temporary ASP.NET Files folder. By default the access permissions are given to the ASP.NET local user account, which has the high-trust permissions needed to access compiled code. It is possible that there were some changes in the default permissions causing versioning conflicts. Another possibility would be that anti-virus software could be locking an assembly inadvertently.
Solution: Clear the Temporary ASP.NET Files Folder of all contents.
I think the Scenario 3 refer to my issue , but the solution is what I want to avoid ,
I dont want to clear the temp folder every time I deploy the website, what I current do is just copy all file to IIS folder and overwrite it.
Description: By default, when an ASP.NET Web application is compiled the compiled code is placed in the Temporary ASP.NET Files folder. By default the access permissions are given to the ASP.NET local user account, which has the high-trust permissions needed to access compiled code. It is possible that there were some changes in the default permissions causing versioning conflicts. Another possibility would be that anti-virus software could be locking an assembly inadvertently.
Solution: Clear the Temporary ASP.NET Files Folder of all contents.
That's MS solutions, as I said, i'll ask my colleagues when I get to the office.
Regards
Regards
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
that did not apply to me , I seems my problem is when I overwrite the dll files in bin folder.
it create additional temp files,
It usually works fine til earlier this year .
I have to remove the
stop iis
remove the temp file
copy the files to bin folder
start the IIS
that means 3 more steps than before even it works.
it create additional temp files,
It usually works fine til earlier this year .
I have to remove the
stop iis
remove the temp file
copy the files to bin folder
start the IIS
that means 3 more steps than before even it works.
Please refer to the link below
http://blogs.msdn.com/b/carloc/archive/2007/06/12/compiler-error-message-cs0433-in-asp-net-2-0.aspx
Regards