Tuesday, September 14, 2004
SharePoint Errors
Ok, I am finding this out the hard way, but I am telling this to everyone so you don’t have to go through the same frustration. The errors that SharePoint gives can be very misleading!
Since yesterday I have been trying to figure out why SharePoint keeps complaining that my web part is not marked as safe even though I have setup the whole site as part of WSS_Medium security and marked the assembly as safe (I have made sure 100s of times that the web.config is correct). Below is the actual error that I was getting:
A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe.
Logically you would think that there is something wrong with how the web part is configured, or maybe there is something wrong with the web.config, or wait it could even be something with the Virtual PC running SharePoint. But… that’s not the case :-/
After spending a long time and after creating several different web parts with several different approaches hoping it would like one (including some with the default names like WebPart1, WebPartLibrary, etc.) I figured out that it was the class constructor!! I mistakenly did not put the scope classifier for the constructor and SharePoint wasn’t able to construct the class, but for some reason it decided that the web part was not marked as safe!
Lesson: be very careful when SharePoint complains, some times the actual problem isn't what it is says it is!
Since yesterday I have been trying to figure out why SharePoint keeps complaining that my web part is not marked as safe even though I have setup the whole site as part of WSS_Medium security and marked the assembly as safe (I have made sure 100s of times that the web.config is correct). Below is the actual error that I was getting:
A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe.
Logically you would think that there is something wrong with how the web part is configured, or maybe there is something wrong with the web.config, or wait it could even be something with the Virtual PC running SharePoint. But… that’s not the case :-/
After spending a long time and after creating several different web parts with several different approaches hoping it would like one (including some with the default names like WebPart1, WebPartLibrary, etc.) I figured out that it was the class constructor!! I mistakenly did not put the scope classifier for the constructor and SharePoint wasn’t able to construct the class, but for some reason it decided that the web part was not marked as safe!
Lesson: be very careful when SharePoint complains, some times the actual problem isn't what it is says it is!
Friday, September 03, 2004
GMail Annoyance
Everyone knows about GMail and most of the people already have GMail accounts. I haven't used my account for quite some time but lately I have noticed that almost everyday somebody is offering a GMail account because they have invitations left.
Do a quick Google search on "GMail invitations" and you will be surprised. All of all, check out this website dedicated to GMail invitations!
I guess this is dedication... but it just annoys me.
Do a quick Google search on "GMail invitations" and you will be surprised. All of all, check out this website dedicated to GMail invitations!
I guess this is dedication... but it just annoys me.
