Well, queue the theme from the "Twilight Zone". I tried taking out the references to the component from the ASPX (and code-behind page.) No dice. Not even when I removed the reference to the project. I tried some other pages and while my VB.NET ASPX pages worked, my C# ASPX pages did not
Then, I rebooted (hmm. I guess I hadn't done that in a while) and now my page (reference-less) worked. So, I started adding stuff back in. First, I just added the reference to the project that builds the component in "Solution Explorer". I got an error about finding another component which the component refers to. So, in "Solution Explorer", I went to my component, removed the reference and added it back. Now my page worked again (once I did a "Rebuild Solution" instead of just a "Build Solution"). Then, I added back everything else
I'm now getting an error from deep inside the component, but that's something I can figure out from here
So, it appears that this issue is closed...just a case of the "creeping crud" in memory
----- Steven Cheng[MSFT] wrote: ----
Hi Lowell
Thanks for posting in the community!
From your description, you found some of your ASP.NET web pages failed to
compile and encountered some certain errors saying there there wasn't
sufficient privilege to access the component that my ASPX page calls,yes
If there is anything I misunderstood, please feel free to let me know
Based on my experience, since you mentioned that the project and components
are well builed, this problem may be caused by some certain security issues
and is a runtime error. Would you please try the following steps
1. Does the problem occur in any other generic web projects or just occcur
in the certain one?
2. If just occur in this particular one, does the problem occurs in every
page or just in some certain pages? If so, can you find any commons of
those certain pages with this problem
3. Since you've also mentioned the "errors saying there there wasn't
sufficient privilege to access the component that my ASPX page calls",
would you please check all the components you've called in those error
pages or in your application? If there is any particular components you've
referenced in the project, you may try remove them(remove the reference or
those certain codes which calls these components) to see whether the
situation will change
Please check out my suggestions. I think it'll be much better for us to
trouble-shoot if we could isolate the problem within a small scope. Also,
if you have any other ideas or new findings, please feel free to let me
know.
Regards
Steven Chen
Microsoft Online Suppor
Get Secure!
www.microsoft.com/securit
(This posting is provided "AS IS", with no warranties, and confers no
rights.