Dustin Miller, with SharePoint Experts, has been kind enough to keep this blog alive since it contains a lot of content. You can access my new site and blog by going to http://www.BobMixon.com.
bmixon's blog
Just another VSPUG – Virtual SharePoint User Group weblog
You are here: Home
Dustin Miller, with SharePoint Experts, has been kind enough to keep this blog alive since it contains a lot of content. You can access my new site and blog by going to http://www.BobMixon.com.
Maybe one of you guru's out there can help me with this one. I am in need of creating a new list definition that has all of the core functionality found in an issues list. This is one list type that I have not extended in the past and find there is a lot of base code. What I don't understand is where and how SP brings list specific and base code together; which I can duplicate in a custom list definition as a starting point. Once I have a base custom list definition with all of the features of an issues list (history is the key), I can take it from there. Anyone care to shed some light on this for me?
Maybe one of you guru's out there can help me with this one. I am in need of creating a new list definition that has all of the core functionality found in an issues list. This is one list type that I have not extended in the past and find there is a lot of base code. What I don't understand is where and how SP brings list specific and base code together; which I can duplicate in a custom list definition as a starting point. Once I have a base custom list definition with all of the features of an issues list (history is the key), I can take it from there. Anyone care to shed some light on this for me?
- December
- 6
- 2005
Modify the Top Navigation Bar in WSS without FrontPage 2003
Posted by bmixon
No Comments »
Todd Bleeker has written a lot about how to use the Content Editor Web Part (CEWP) to make modifications to your Sites. I personally like this approach for many reasons; many companies don't let users edit Sites with FrontPage, FrontPage has some quirks that can make support a real issue, very easy to break your sites, ghosting/unghosting, blah, blah, blah….
So I ran into a question today asking if it is possible to modify the top navigation bar of a WSS Site? The most common answer is to open FrontPage 2003. right-click on the nav bar itself and make whatever modifications you wish. What about when you don't have FrontPage 2003? Well, using Todd Bleekers CEWP approach, here is how you can hide the Help link on the Top Navigation Bar:
- Place a CEWP t the bottom of your page and configure the properties so it is hidden; i.e. no border or title.
- Click on the 'Source Editor…' button and enter the following code:
Save you CEWP and you will see the Help link is gone.
I currently use the Internet Explorer Developer Toolbar to determine what element ID's are available for me to work with. Here is a list of what the default ID's are in the top navigation bar:
onettopnavbar1002-0 = Home
onettopnavbar1002-1 = Documents and Lists
onettopnavbar1002-2 = Create
onettopnavbar1002-3 = Site Settings
onettopnavbar1002-4 = Help
- December
- 6
- 2005
Modify the Top Navigation Bar in WSS without FrontPage 2003
Posted by bmixon
No Comments »
Todd Bleeker has written a lot about how to use the Content Editor Web Part (CEWP) to make modifications to your Sites. I personally like this approach for many reasons; many companies don't let users edit Sites with FrontPage, FrontPage has some quirks that can make support a real issue, very easy to break your sites, ghosting/unghosting, blah, blah, blah….
So I ran into a question today asking if it is possible to modify the top navigation bar of a WSS Site? The most common answer is to open FrontPage 2003. right-click on the nav bar itself and make whatever modifications you wish. What about when you don't have FrontPage 2003? Well, using Todd Bleekers CEWP approach, here is how you can hide the Help link on the Top Navigation Bar:
- Place a CEWP t the bottom of your page and configure the properties so it is hidden; i.e. no border or title.
- Click on the 'Source Editor…' button and enter the following code:
Save you CEWP and you will see the Help link is gone.
I currently use the Internet Explorer Developer Toolbar to determine what element ID's are available for me to work with. Here is a list of what the default ID's are in the top navigation bar:
onettopnavbar1002-0 = Home
onettopnavbar1002-1 = Documents and Lists
onettopnavbar1002-2 = Create
onettopnavbar1002-3 = Site Settings
onettopnavbar1002-4 = Help
I work in an environment that is very fast paced. As a result, I am not always afforded the time to do things correctly, or the way I wish, the first time.
I have a number of assemblies that contain code shared across many Web Parts. In the past, I always placed these shared assemblies in the GAC simply because it was the "easy way out". I had some extra time and thought it would be a good idea to finally get those assemblies out of the GAC and moved into a more secure area; welcome to the BIN directory! I have a fairly good understanding of Code Access Security (CAS); building permission sets and code groups allowing code to run in the proper security context. But for the life of me, I still had problems. No matter what I did, I would receive an error indicating "Execution permission cannot be acquired".
I scratched my head, reviewed my code; to see who was naughty and who was nice. Still nothing, I couldn't find anything wong with my permission set and/or permission elements in my config file. So I dropped Maurice Prather an e-mail and he quickly pointed me in the right direction. Knocking my head on my desk; does AllowPartiallyTrustedCallers ring a bell Bob?
The shared assemblies were running in the GAC which gives FullTrust to them. That's actually the problem with running code in the GAC; anyone, trusted or not, can call your code. Pulling the assemblies out of the GAC and placing them in the BIN directory changed the manner in which they were being called. So here is what needs to be done.
- Open the AssembleInfo.cs file for your shared assembly.
- Make sure you have included the 'using System.Security' reference.
- Anywhere in that file add the [assembly:AllowPartiallyTrustedCallers] assembly attribute. For more information on this assembly attribute, see MSDN : AllowPartiallyTrustedCallersAttribute Class.
- Recompile, deploy the assemblie(s) and reset IIS.
That's all there is to it. Too simple, but it took time out of my day so I thought I would share it with you! Thank you Maurice for all the help!
I work in an environment that is very fast paced. As a result, I am not always afforded the time to do things correctly, or the way I wish, the first time.
I have a number of assemblies that contain code shared across many Web Parts. In the past, I always placed these shared assemblies in the GAC simply because it was the "easy way out". I had some extra time and thought it would be a good idea to finally get those assemblies out of the GAC and moved into a more secure area; welcome to the BIN directory! I have a fairly good understanding of Code Access Security (CAS); building permission sets and code groups allowing code to run in the proper security context. But for the life of me, I still had problems. No matter what I did, I would receive an error indicating "Execution permission cannot be acquired".
I scratched my head, reviewed my code; to see who was naughty and who was nice. Still nothing, I couldn't find anything wong with my permission set and/or permission elements in my config file. So I dropped Maurice Prather an e-mail and he quickly pointed me in the right direction. Knocking my head on my desk; does AllowPartiallyTrustedCallers ring a bell Bob?
The shared assemblies were running in the GAC which gives FullTrust to them. That's actually the problem with running code in the GAC; anyone, trusted or not, can call your code. Pulling the assemblies out of the GAC and placing them in the BIN directory changed the manner in which they were being called. So here is what needs to be done.
- Open the AssembleInfo.cs file for your shared assembly.
- Make sure you have included the 'using System.Security' reference.
- Anywhere in that file add the [assembly:AllowPartiallyTrustedCallers] assembly attribute. For more information on this assembly attribute, see MSDN : AllowPartiallyTrustedCallersAttribute Class.
- Recompile, deploy the assemblie(s) and reset IIS.
That's all there is to it. Too simple, but it took time out of my day so I thought I would share it with you! Thank you Maurice for all the help!