Please fix the following issues to continue: We encountered an unexpected error. Please try again later. If this issue continues, please contact site support.

Question

Please fix the following issues to continue: We encountered an unexpected error. Please try again later. If this issue continues, please contact site support.

iqworks Information Quality Works 331

i am getting this error when working with this forum post :

https://learn.microsoft.com/en-us/answers/questions/1471083/the-type-or-namespace-name-linq-does-not-exist-in

thanks for any help

AgaveJoe 30,126 Reputation points

2023-12-30T16:23:32.1466667+00:00

In your previous thread, you were asked to provide a code example. You have to understand that the community cannot debug your code without enough code to reproduce this issue.

Anyway, I'm guessing there is a problem with the upgrade approach (site to application). Perhaps the blog will help figure out where the mistake is located.

https://devblogs.microsoft.com/dotnet/converting-a-web-site-project-to-a-web-application-project/

Also, did you check of the DLL exists in the bin folder?
iqworks Information Quality Works 331 Reputation points

2023-12-30T21:37:14.2366667+00:00

if you look at the initial thread, you will see that i DID include a print of the dll's added to the references. I have no reason to believe it is an issue with the conversion, unless I see otherwise.

as far as needing help with the code, i didnt ask for that. if you reread the post you will see that i was ASKED to supply a sample of the code. since i didnt know what a sample meant, i included all the code in that program. I was ONLY interested in the original request, that is, why was I getting this error when the references needed were already IN the references folder.

thanks for your help.

3 answers

Your answer

AgaveJoe 30,126 Reputation points

2023-12-30T16:23:32.1466667+00:00

In your previous thread, you were asked to provide a code example. You have to understand that the community cannot debug your code without enough code to reproduce this issue.

Anyway, I'm guessing there is a problem with the upgrade approach (site to application). Perhaps the blog will help figure out where the mistake is located.

https://devblogs.microsoft.com/dotnet/converting-a-web-site-project-to-a-web-application-project/

Also, did you check of the DLL exists in the bin folder?
iqworks Information Quality Works 331 Reputation points

2023-12-30T21:37:14.2366667+00:00

if you look at the initial thread, you will see that i DID include a print of the dll's added to the references. I have no reason to believe it is an issue with the conversion, unless I see otherwise.

as far as needing help with the code, i didnt ask for that. if you reread the post you will see that i was ASKED to supply a sample of the code. since i didnt know what a sample meant, i included all the code in that program. I was ONLY interested in the original request, that is, why was I getting this error when the references needed were already IN the references folder.

thanks for your help.

Answer 1

iqworks Information Quality Works 331

if you look at the initial thread, you will see that i DID include a print of the dll's added to the references. I have no reason to believe it is an issue with the conversion, unless I see otherwise.

as far as needing help with the code, i didnt ask for that. if you reread the post you will see that i was ASKED to supply a sample of the code. since i didnt know what a sample meant, i included all the code in that program. I was ONLY interested in the original request, that is, why was I getting this error when the references needed were already IN the references folder.

thanks for your help.

AgaveJoe 30,126 Reputation points

2023-12-30T22:28:58.95+00:00

if you look at the initial thread, you will see that i DID include a print of the dll's added to the references. I have no reason to believe it is an issue with the conversion, unless I see otherwise.

No, you shared a library reference.

The error message clearly states there is a problem with the lqLinqDataClasses.designer.cs file within the App_Code folder. Most likely this is a bug created when converting from a web site to a web application. Code in the App_Code folder is compiled at runtime and therefore is only used in web site projects. Web application do no need an App_Code folder because all classes and code behind files are compiled into a single DLL and copied to the bin folder. Web Applications do not contain source code on the server like you find with a Web Site project. Only the dll and aspx pages are deployed.

Again, if we could see your code we would have an idea of what you're doing...

Shared Code Folders in ASP.NET Web Sites

as far as needing help with the code, i didnt ask for that. if you reread the post you will see that i was ASKED to supply a sample of the code. since i didnt know what a sample meant, i included all the code in that program. I was ONLY interested in the original request, that is, why was I getting this error when the references needed were already IN the references folder.

The first step in debugging is reproducing the problem. I'm unable to reproduce this problem. My test web application work perfectly.

Did you at least read the link I provided which covers how to migrate a web site to a web application? I assume you made a few mistakes along the way. Having an App_Code namespace is a clue that the conversion was not done correctly.

Answer 2

iqworks Information Quality Works 331

The issue with this post is that i got an error while trying to add an answer to the actual post itself.

Answer 3

iqworks Information Quality Works 331

AgaveJoe, great explanation! I will read your link, I believe that will help me much.

also, i see you asked for the code, i put it in a text file rather than add all that code to this post (which, i believe caused the "please contact site support" error)

iqLinqDataClasses.designer.cs.txt

forum post reference does exist

Share via

Please fix the following issues to continue: We encountered an unexpected error. Please try again later. If this issue continues, please contact site support.

3 answers

Your answer