error CS0433: The type 'ucTerms' exists in both 'c:\Users\satyajit.singh\AppData\Local\Temp\Temporary ASP.NET Files\eoc\f63b2378\43228109\App_Web_cez09cff.dll' and 'c:\Users\satyajit.singh\AppData\Local\Temp\Temporary ASP.NET Files\eoc\f63b2378\43228109\App_Web_frn_iozf.dll'
I can see that theere is a User Control "ucTerms" which is contained in the "User Control" folder under also under the root (main solution) . I researched a lot and tried different solutions like setting the "batch = false", deleting the temporary folder but none have worked.
The web site builds successfully but this error pops up when I try to publish the website.
can anyone help me on this. I have been working on this error for last 3 days.
Thanks in advance,
Satyam
have you tried these?
Error: The type exists in both directories,
http://www.pgs-soft.com/the-type-x-exists-in-both-y1-dll-and-y2-dll.html,
http://forums.asp.net/t/980517.aspx
if none of these help, try to isolate the issue:
remove your user control from the project (make sure you save it somehwere else) to see if its only this one user control that has the issue, or every other one as well, this information may be helpful
Related
So I am just in utter disgust at what happened. i was working on an asp.net in TFS application and all of the sudden it literally just stopped working. Every time I tried to launch it in a browser it would display this error:
The entire DESCRIPTION states:
Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make
sure that it is spelled correctly
I haven't the slightest clue what happened. I have not to my best recollection done anything to jeopardize it.
This is what I've done. since I have two different logins to my computer, I took the solution and tried to launch it in my 2nd login and it worked perfectly. I took that same solution file and tried to launch it in my current login and it's causing this issue.
I reset all my Visual studio settings and tried to launch the solution and again - get the same error.
It is showing the SERVIER ERROR in /HOME.aspx - but this error does not show up in my other login.
Does anyone have any idea what could cause this? I'm basically looking at creating a new user profile for myself to get this resolved. Any help will be much appreciated.
Could it be my user profile or would simply re-installing VS could resolve it?
I was just about finished a new website I've created but as I was fixing an error on a page I've called view-items.aspx I got a compilation error saying a variable is not declared but I haven't touched that part of the code and it WAS working. I now can't even bring the homepage up (default.aspx) as it still gives me the compilation error for view-items.aspx !! Out of desperation I deleted view-items.aspx and I'm STILL getting the same error regarding a variable not declared for a page that now does not exist !! I am using 1&1 hosting with Asp.Net and VB. Any suggestions please ?
Ah.. Stupidity !! I had accidentally uploaded the file to the APP CODE folder causing all sorts of problems, when I deleted that it works fine. Thank you
I currently have DNN 7 installed and have been unable to get your module to work.
I do a typical module install of 2sic_2SexyContent_08.04.07_Install with apparently no issues.
When I drag the Content module to a pane there's an exception created in the log although the module does show up on the page.
I then click "Auto configure..." and then OK in the pop-up
It shows "installing Getting Started Templates" but then a pop-up shows error 500
The log shows:
"The given key was not present in the dictionary" and "Object reference not set to an instance of an object."
I checked github but couldn't find a resolution.
Is there an easy fix to this as I'd really like to get this installed. Heck, even if it's not easy, I still want to get it installed.
Thanks
Bob
I created a short video for you so you see what you should get: http://2sxc.org/en/blog/post/moving-discussions-from-codeplex-to-stack-overflow
Here another guess
make sure your domain-names/paths are correct in DNN - these are portal settings and if something is wrong there, you will probably get funny redirects
Also: pls post some screenshots etc. - because that will help to understand which part is generating a 500
Note that it's also possible that whatever caused the initial error, did something which is hard to fix for inexperience users. So just to start, it's probably best to first create a new DNN, install 2sxc and when that works, figure out what is different in the two installs.
When I tried to modify Microsoft forefront Unified access login.asp page and pages that comes with it ,
I prepared my custom files for css; inc files ; InstallAndDetect ..etc
but When i inserted those files under CustomUpdate folders i got this error :
" An error occurred on the server when processing the URL. Please contact the system administrator. "
I tried files i prepared before by putting them in the place of the default files propvided by the system.
Ofc the naming is respecting when using customupdate files!!
Do you have any idea how can I solve this issue??
I'm afraid I don't have a proper picture of what exactly might have caused the problem in your case.
But I just went through resolving the same error message on my system (2012 R2, IIS 8) (while searching for the solution I came across your post)
And it turned out that what was causing my problems was the use of classic ASP parent paths (with "../" in them)
Switching to absolute and virtual paths solved the issue for me.
See here: http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/classic-asp-parent-paths-are-disabled-by-default
Thank you for your answer.
Actually there was a bug with the product itself.
It didn't recognize the path to the CustomUpdate folder for any of custom folders in InternalSite folder.
I had to ask for a hot fix from Microsoft support to be able to use customized files (CSS , asp, images ).
Once the fix was installed, everything was working fine and I was able to see the customization I have done to the login page.
I've had this intermittent issue when using asp.net. My site is dynamically compiled. Sometimes when I modify a user control my web site complains that it is defined in multiple places. It almost seems like the old control did not get removed from the asp.net temporary files and the updated control is compiled to the same directory so it's defined in multiple places. That would make sense to me except for the fact that I have no control over what is in the Temporary ASP.net Files folder.
I've read that having circular references will cause this. I've made sure that I don't have circular references. Even with the simplest site I've seen this happen.
I've noticed that when using Master Pages this error seems to come up a lot more frequently.
I've read that a hotfix tries to fix this issue but I've gotten this error after applying the hotfix.
If I get the file causing the issue and make an edit to it then the error goes away. Even if I just put a space in the file it will resolve the error.
I can also get the error to resolve sometimes by visiting other pages of the site that might not use the user control and hitting refresh. This does not always work.
If I set the site to debug the error never happens. If I set it so that it comiles on a page by page basis then the error does not happen as much but still happens.
Below is what the error looks like.
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: CS1595: '_ASP.Header_ascx'
is defined in multiple places; using definition
from 'C:\WINNT\Microsoft.NET\Framework\v1.0.3705\Temporary
ASP.NET Files\root\afwew23d\asdfasd423\asdf23.dll'
Edit:
I'm using .net 2.0 (3.5) even though the error above says 1.0. I got that error from another source since I can't reproduce the issue every time. But the type of error is the same.
Edit 2:
Thanks gisresearch for your research. There was one statement in the link you provided:
One caution even if you have debug=false, is that if you go in and change something in one of your aspx pages, this page will have to be recompiled, but this doesn’t cause an appdomain reload so the whole application is not batch compiled again. This has the effect that the page will now get recompiled separately and get its own dll, so don’t change your aspx pages on a live server too often.
There is a setting in machine.config determining how many recompiles are allowed before the app domain restarts, by default it is set to 15, so after 15 recompilations the app domain will restart, just as it would if you touched the web.config or touched the bin directory.
This seems to say that when debug=false and the site has already been visited and compiled, if you change a page it will only compile that one page. That sounds like it could cause problems. I had thought changing a page or user control would cause the entire app to recompile.
Do you have two user controls with the same file name in diferent Folders of your Web App?
That sometimes will cause this issue.
If I set the site to debug the error
never happens.
when debug=true, the asp.net compiler don’t batch compile, when debug=false it does batch compile and may cause this issue.
The Read this post.
There is a conversation about the same issue.
re: ASP.NET Memory: If your application is in production… then why
is debug=true Monday, April 24, 2006
2:39 PM by Robbie Coleman We did get
an error for a UserControl that it
reported it could not load the
FileName_ascx class due to multiple
versions in the Temp ASP.NET folder.
We identified that we had two user
controls with the same file name in
diferent Folders of the same Web App.
The also had diferent namespaces and
never through this exception until we
set debug="false". We even wiped the
Temp ASP.NET directory clean on an
IISreset.
The only way we could fix the error,
was by renaming the ascx file of one
of the two.
Is this correct...? Was there a better
way to fix this?
BTW... [KissUpText] Tess, your posts
have been very helpfull to our
development team, and we really
appreciate all the information you
have given away. [/KissUpText]
re: ASP.NET Memory: If your application is in production… then why
is debug=true Tuesday, April 25, 2006
1:56 AM by Tess Hi Robbie,
Thanks for the nice comment:)
I am assuming that you are getting
"CS1595:
'UserControls.WebUserControl2' is
defined in multiple places; using
definition from
'c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
ASP.NET
Files\usercontrols\293a1a4b\dbb2d387\cisxatg3.dll'
" or similar.
The problem basically occurrs if you
are using src rather than CodeBehind
and your cs or vb files contain a
definition for exactly the same class
in exactly the same namespace. The
error is really the same as what you
would get if you tried to compile a
dll with another class defined twice
in the same namespace.
The reason i am saying it happens when
you use src is because if you would
use CodeBehind you would have gotten
an error at compile time.
If the usercontrols are really the
same I would avoid creating a copy,
and instead using the one from the
other folder. If they are different I
would either give the different names
if possible, and if not, make sure
that the source classes are in
different namespaces, such as
ProjectName.FolderName.MyUserControl
The reason you are seeing it now and
not before is because you are now
batch-compiling everything into one
dll.
Hope this helps.