Tuesday, December 21, 2010
Let's start at the beginning
Simple deploy description
I have a bunch of posts that relate to deploying a webpart.
Building a webpart is not real tricky - it's a standard ".net"
dll that inherits form System.Web.UI.WebControls.WebParts or alternatively - Microsoft.SharePoint.WebPartPages.WebPart which are related classes.
So if you're old enough to remember cgi - that means
at one time interactive web pages were done with a perl
script that was connected to the server via a real simple
mechanism --- there was a directory it went into and the server
dealt with the issue of connecting your perl script to
the html. Of course that was then and now is now.
Here is another link by Sahil Malik for deployment.
Now, a quick view of these two posts will let you realize that they're putting
the DLL into two different directories. Actually there are at least
three different areas I've seen referenced to put the dll - and then
of course you can "package" your solution in different ways. I'm
guessing they wanted to be flexible with their solutions here.....
So --- _app_bin in the inetpub directory --- bin in the sharepoint
directory or gac ????? and why is that ????? this is a working mystery ---
that I very much would like to have an answer to. Nevertheless, I will
keep digging and if anybody is holding their breath ---- ( maybe you
shouldn't ). My guess is somebody on the sharepoint dev team knows
why. Really this should not be a cause for anxiety. This stuff does
work ---- mostly. Sometimes it's not really important that you know
why.... although I should mention that most of the time I let
myself get along without that bit of info - and finds that it will
come back to bite me - any guess on where?
I have a bunch of posts that relate to deploying a webpart.
Building a webpart is not real tricky - it's a standard ".net"
dll that inherits form System.Web.UI.WebControls.WebParts or alternatively - Microsoft.SharePoint.WebPartPages.WebPart which are related classes.
So if you're old enough to remember cgi - that means
at one time interactive web pages were done with a perl
script that was connected to the server via a real simple
mechanism --- there was a directory it went into and the server
dealt with the issue of connecting your perl script to
the html. Of course that was then and now is now.
Here is another link by Sahil Malik for deployment.
Now, a quick view of these two posts will let you realize that they're putting
the DLL into two different directories. Actually there are at least
three different areas I've seen referenced to put the dll - and then
of course you can "package" your solution in different ways. I'm
guessing they wanted to be flexible with their solutions here.....
So --- _app_bin in the inetpub directory --- bin in the sharepoint
directory or gac ????? and why is that ????? this is a working mystery ---
that I very much would like to have an answer to. Nevertheless, I will
keep digging and if anybody is holding their breath ---- ( maybe you
shouldn't ). My guess is somebody on the sharepoint dev team knows
why. Really this should not be a cause for anxiety. This stuff does
work ---- mostly. Sometimes it's not really important that you know
why.... although I should mention that most of the time I let
myself get along without that bit of info - and finds that it will
come back to bite me - any guess on where?
What is sharepoint?
I think that sharepoint - starts out very simple - as
a collaborative file system --- utilizing mostly http -
and of course built on an asp.net framework. And that's
great. But it turns out that a piece of software that
was built with the degree of indirection
contained within the sharepoint framework can't really
maintain a very limited application scope - especially
when a large development community gets a hold of it.
I can say a few things that might give you a little better
picture. It's a big box - that's fairly stable -
but highly tweak-able. ( somebody actually thinks that
tweak-able is a word ).
Nevertheless, there are downsides. Although there is a lot
of documentation and many blogs --- someday I will try and
organize what I've found out there --- there is no simple
guide to sharepoint that is both exhaustive or complete -
so it tends to be a bit of a free for all.
As an example of this, one very important feature of sharepoint
is the web part. I think there was a concept of web parts before
sharepoint - but sharepoint and web parts are very interconnected -
and while they are easy to use - really understanding this
mechanism is a little more challenging. To be clear about
this --- there is a mechanism for creating and deploying
web parts --- and from my point of view this process and mechanism
is all a bit murky for me at this point and in the next few
posts I'm going to focus on this and see if there is
really a bottom to this rabbit hole.
a collaborative file system --- utilizing mostly http -
and of course built on an asp.net framework. And that's
great. But it turns out that a piece of software that
was built with the degree of indirection
contained within the sharepoint framework can't really
maintain a very limited application scope - especially
when a large development community gets a hold of it.
I can say a few things that might give you a little better
picture. It's a big box - that's fairly stable -
but highly tweak-able. ( somebody actually thinks that
tweak-able is a word ).
Nevertheless, there are downsides. Although there is a lot
of documentation and many blogs --- someday I will try and
organize what I've found out there --- there is no simple
guide to sharepoint that is both exhaustive or complete -
so it tends to be a bit of a free for all.
As an example of this, one very important feature of sharepoint
is the web part. I think there was a concept of web parts before
sharepoint - but sharepoint and web parts are very interconnected -
and while they are easy to use - really understanding this
mechanism is a little more challenging. To be clear about
this --- there is a mechanism for creating and deploying
web parts --- and from my point of view this process and mechanism
is all a bit murky for me at this point and in the next few
posts I'm going to focus on this and see if there is
really a bottom to this rabbit hole.
Tuesday, November 9, 2010
SPSERVICES - Marc Anderson
Marc Anderson is a sharepoint developer and educator who
has done a lot of work developing custom data solutions for sharepoint.
One of his major contributions is a jquery library that is
described in some post at:
A jQuery Library for SharePoint Web Services (WSS 3.0 and MOSS): Part 2 – How Does It Work?
The main location for this code is at:
SPServices - Codeplex
He also has a series of articles on xsl - xslt and dvwp
at Endusersharepoint.com where part 1 of his spservices
article is:
A jQuery Library for SharePoint Web Services (WSS 3.0 and MOSS): Real World Example – Part 1
has done a lot of work developing custom data solutions for sharepoint.
One of his major contributions is a jquery library that is
described in some post at:
A jQuery Library for SharePoint Web Services (WSS 3.0 and MOSS): Part 2 – How Does It Work?
The main location for this code is at:
SPServices - Codeplex
He also has a series of articles on xsl - xslt and dvwp
at Endusersharepoint.com where part 1 of his spservices
article is:
A jQuery Library for SharePoint Web Services (WSS 3.0 and MOSS): Real World Example – Part 1
Monday, November 8, 2010
css - Heather Solomon
This is a link to Heather Solomon's blog
which contains a reference for sharepoint css.
css reference
which contains a reference for sharepoint css.
css reference
volume one - why is there sharepoint
why is there sharepoint??????
does it help developers?
===> maybe
does it help microsoft
??? I'm really not sure they need the money
does it help the end users?????
I'd like to think that is does /////
Does it help managers ------
I hope so .....
does it help developers?
===> maybe
does it help microsoft
??? I'm really not sure they need the money
does it help the end users?????
I'd like to think that is does /////
Does it help managers ------
I hope so .....
Subscribe to:
Posts (Atom)