Monthly Archives: Desember 2007

Hugsun Um auglýsing vara

2 Svör

I put up a SharePoint Designer extensions project up at CodePlex earlier this year and even though it’s really quite limited in scope, I estimate that it’s been downloaded by 40 að 60 (possibly even 100) companies in just about two months. That indicates to me that there’s a market for that solution and if I were to successfully commercialize it, that could translate into a goodly amount of beer 🙂

My background is actually much more in product development and I know what is required to bring a top-notch product, as opposed to a CodePlex hobby project, to market. In my past life, I was responsible for product R&D for all software products. The difference between then and now is that I’m a consultant now working for an (excellent) consulting firm (Conchango). Áður, I had an entire company behind me and in front of me, selling and supporting the products we brought to market. Í dag, I’d be alone.

I have several product ideas in mind, but I think the easiest would be to create a commercial version of the above-mentioned CodePlex project that uses that as a starting point and extends it further. My fuzzy off-the-cuff thinking is to charge something like $100 for an unlimited developer license and $500 per production web front end. I think I would also give away the source code.

If you have thoughts or experiences that you’re willing to share, vinsamlegast eftir umsögn eða email me directly. I’d like to hear opinions like:

  • Is it all worthwhile?
  • Practical suggestions for marketing, collecting money, distributing.
  • Pricing.
  • Stuðningur.
  • Any other comment you’d like to leave.

It’s "easy" to come up with product ideas and to implement them, though many dozens of hours of work are required. The other stuff is not as easy for me.

</enda>

Technorati Tags:

Sunnudagsmorgun Funny: “Jesús Must Die”

1 Svara

We bought our first (and only) "luxury" car back when hurricane Floyd nailed the east coast of the U.S. We got a LOT of rain here in New Jersey and several days passed before life returned to normal. Just before Floyd struck, we made an offer for a used Volvo 850 GL and after Floyd struck, drove it home.

It was our first car with a CD player. Like most new car owners, we went a little CD crazy, revived our dormant CD collection and went on long drives just to listen to CD’s in the car. Like all fads, this passed for us and we ended listening to the same CD over and over again. Í okkar tilviki, it was Jesus Christ Superstar.

Eitt af því sem (margir) brilliant pieces in that rock opera is sung by the establishment religious types, led by Caiaphas, the "High Priest". They sing their way into deciding how to handle the "Jesus problem" and Caiaphas directs them to the conclusion that "Jesus must die". The refrain on the song is "Just must die, must die, must die, this Jesus must die". You hear that refrain a lot in that piece.

At the time, my son was about three years old. You can probably see where this is going.

I came home from work one day and my son is in the living room playing with toys and humming to himself. I’m taking off my jacket, looking through the mail and all my usual walk-in-the-door stuff and I suddenly realize that he’s just saying, not really singing: "Jesus must die, must die, must die." I was mortified. I could just see him doing that while on one of his baby play dates at a friend’s house — probably the last play date with that baby friend.

We pulled that CD out of the Volvo after that 🙂

</enda>

Google gerði Samþykkja Live Spaces Blog mína í AdSense

7 Svör

UPDATE: Frá 03/09, I have found no way to integrate my live spaces account with Google Adsense. Microsoft’s system here seems to prevent all of the technical mechanisms that Google provides would-be adsense hosters. I tend to believe this is mainly a side effect of the security they’ve built into live spaces, not a direct effort to disable Adsense.

Þetta er ekki SharePoint staða, en gæti verið áhugaverð fyrir bloggara gen heimsókn.

Someone commented on their Windows Live Spaces blog that Google affirmatively denied their application to participate in AdSense. She theorized that Google denied her because Windows Live Spaces hosts her blog. Hins, Ég var nýlega samþykkt inn í forritið fyrir lifandi rými mínir blogg, svo stefnan hefur annaðhvort breytt eða Google hafnað henni af öðrum ástæðum.

Auðvitað, Ég sé ekki neina augljósa leiðin til að fella Google AdSense í lifandi rými mitt, but it’s a start 🙂

</enda>

Technorati Tags: ,

Framkvæmd Master / Detail Sambönd nota sérsniðna Lists

5 Svör

Forum notendur oft og spurningum eins og þetta:

> Halló,
>
> Vinsamlegast segðu mér ef það eru einhverjar möguleikar til að byggja upp sérsniðna lista með
> skipstjóri og gerð upplýsinganna (eins reikningum) án þess að nota Infopath.
>

SharePoint afla sumir út af the kassi lögun sem styðja konar kröfur fyrirtækis eins og þessi.

Almennt, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Nota fleiri listum til að halda viðskiptavinar Reikningur, vörunúmerum, o.fl..

Notaðu fyrirspurn efni vefur hluti (í mosa aðeins) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) er einnig í boði fyrir skýrslugerð hlið hennar.

Hins, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

  • Stærð tengdum útlit listum vs. "smartness" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 atriði, that’s going to be a problem. The lookup control does not page through those items. Staðinn, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
  • Lookups "pull back" one column of information. You can never pull back more than one column of information from the source list. Til dæmis, you cannot select a customer "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
  • No intra-form communication. Ég hef skrifað um þetta hér. You can’t implement cascading drop-downs, skilyrðum virkja / slökkva reiti, o.fl..
  • No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. Til dæmis, SharePoint leyfa þér að búa til tvær sérsniðnar lista, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Þá, you can delete the customer from the list. Út af the kassi, there is no way to prevent this. To solve this kind of problem, þú myndir venjulega nota atburði dýraþjálfari.

Það kann að virðast hráslagalegur, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, SharePoint gerir okkur að fylla þær eyður nota tæki svo sem eins og:

  • Event handlers. Use them to enforce referential integrity.
  • Custom dálka: Create custom column types and use them in lieu of the default lookup column. Add paging, höggdeyfir og AJAX lögun til gera þá móttækilegur.
  • BDC. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

    BDC er MOSS lögun (ekki í boði í WSS) and is challenging to configure.

  • ASP.NET vefform: Búa til fullur-lögun AJAX-virkt form sem notar SharePoint mótmæla líkan og / eða vefur þjónusta til að nýta SharePoint listi en að veita mjög móttækilegur notendaviðmót.

Síðasti valkostur getur finnst eins og þú ert að byrja frá grunni, en íhuga þá staðreynd að SharePoint vettvang byrjar þú burt með the hópur stuðningsmanna lykill lögun:

  • Öryggi líkan með viðhald.
  • Matseðill kerfi með viðhald.
  • "Master table" (i.e. Raða listum) með öryggi, innbyggður-í viðhald og endurskoðun.
  • Leita.
  • Back End Integration verkfæri (BDC).

Ef þú byrjar með nýja auða verkefni í Visual Studio, þú hafa a einhver fjöldi af grunngerð og pípulagnir að byggja áður en þú nálgast það SharePoint býður.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, vinsamlegast eftir athugasemd.

</enda>

Quick Ábending: Efni Fyrirspurn Web Part, Leit column value og XSL

3 Svör

I have a column name in a content type named "Real Estate Location".

That column is of type "lookup".

Ég hef breytt <CommonViewFields> og ItemStyle.xsl að sýna dálk.

Einföld <XSL:gildi-af velja =…> skilar til baka innri gildi sem felur Ordinal gögn stöðu, svo sem eins og:

1;#Miami

Til að fá manna-vingjarnlegur gildi, nota XSL hlutstreng-eftir, eins og sýnt:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:gildi-af>

Use this technique whenever you are working with lookup values in XSL transforms and need to get the human-friendly value.

<endir />

Technorati Tags: , ,

SharePoint Beagle desember Útgáfudagur Up & Lifandi

Skildu eftir skilaboð

Margir af þú veist þetta nú þegar, en í desember útgáfu SharePoint Beagle er lifandi.

Sérhver hlutur er þess virði að lesa að mínu mati.

Ég vil gefa smá auka högg til Samstarfsmaður minn er grein (Natalya Voskrensenskya). She provides a screen-shot extravaganza while describing how she used custom lists, workflow, SharePoint Designer, data views and other elements to implement a self-service training feature in MOSS. She describes techniques that can be applied in many different business scenarios. Check out bloggið hennar meðan þú ert á það.

Ekki gleyma að kíkja minn hlutur as well 🙂 I wrote about using MOSS to help an HR department manage open positions.

</enda>

MOSS segir mér “Aðgangur óheimill” að breyta Workflow verkefni, En ég virkilega hafa aðgang

2 Svör

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. allir). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, það getur úthluta verkefnum til fólks.

Ég brjóta leyfi fyrir eyðublöð bókasafn og verkefnalista svo að allir staðfest notandi getur búið til eyðublöð og uppfæra úthlutað verkefnum sínum.

I test with my low-privileges test account.

Get ég að fylla út og vista mynd á bókasafnið? –> YES

Get ég nálgast það verkefni frá netfangatengil? –> YES

Get ég séð Breyta workflow verkefni tengilinn –> YES

Get ég smellt á þessi hlekkur? –> NO … Aðgangi hafnað.

Hvers vegna get ég séð breyta tengilinn sem afneitar mér leyfi þegar ég smelli á það? That’s not how it’s supposed to work…

Ég fara í gegnum öryggi stillingar aftur, very closely. I do it again. Ég tel að eyða þessari færslu því ég augljóslega veit ekki neitt um öryggi.

Lokum, I search the Internets. I find this highly unlikely MSDN forum thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1838253&SiteID=17

Veggspjöldin virðast vera að leggja til að einfalda athöfn að flytja workflow til a ökuferð fati mun ákveða MOSS öryggi tölublað? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 samsæri þar Stan er að biðja Preznit okkar, "Really?" over and over again.

Svo, ekkert til að tapa, Ég eldur upp SPD, hægri-smella á workflow og vista það til c minn:\ drive. That would be the c:\ drive on my laptop. I’m looking over my shoulder the whole time so that no one will ask me, "why are you saving that workflow to your laptop?"

Ótrúlega, that solves my problem. I can edit the task.

Ég tilnefna hér með þetta að vera mest furðulega Workflow Lausn á 2007.

</enda>

Technorati Tags:

SharePoint Designer, Núverandi atriðisins “Kóðuð Absolute URL” og HTTPS

4 Svör

We often want to send an email that includes a hyperlink to the item or document that triggered the workflow. We can use current item’s "Encoded Absolute URL" for this purpose. Hins, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

mynd

Eins og langt eins og ÉG vita, there is no out of the box solution to this problem. If you need to use HTTPS, þú hefur ekki út af the kassi valkostur.

Að leysa það, create a custom action that provides a string replace function to use in your workflow. Alternatively, nota 3 aðila tól svo sem framúrskarandi pakka hér: http://www.codeplex.com/spdwfextensions 🙂

</enda>

Fljótur og Þægilegur: Ákveða Innri Column Nafn a Site dálki

3 Svör

UPDATE: Jeremy Thake has blogged about this and put up some code for a console application that shows internal names.

I was trying to get a content query web part to display a due date from a task and because the screen label is "Due Date", I ráð fyrir að dálkheiti til að nota í <CommonViewFields> is "Due_x0020_Date".

Wrong!

The real column name in this case was "DueDate".

How did I find it? I re-read Heather Solomon’s blog entry on modifying CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. At least, it was correct for me. I did not trust it at first for another column with a much longer name.

I say "Trust it" because I did not trust it and probably wasted near two hours butting my head up against a wall. After I resolved the "DueDate" nafn, I wanted to add another field to <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

I thought to myself, that’s clearly a truncated name. I went ahead and un-truncated it with no success. I finally used the seemingly truncated name and it worked.

Bonus tip: When I was working with the CQWP, if I added a bad internal name to <CommonViewFields>, the CQWP would tell me that the query had returned no results. En, if I added a data type to the field name, it would return a result. Adding the data type actually masked a problem since I was referencing a non-existent field. I could add it, but when I tried to display its value, I would always get a blank.

This did not mask the error:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

This did mask the error:

<CommonViewFields>Due_x0020_Date,DateTime;</CommonViewfields>

</enda>

Varast Breaking Breytingar á ItemStyle.xsl

Skildu eftir skilaboð

Ég var að vinna með ItemStyle.xsl að sérsníða útlit af a Fyrirspurn Content Web Part og rétt um hádegi, I made a breaking change to the xsl. I didn’t realize it, but this had far reaching effects throughout the site collection. I went off to lunch and upon my return, tekið þessi skilaboð birtast í fullt af stöðum:

Ekki tókst að birta þetta Web Part. Til að leysa vandann, opna þessa vefsíðu í Windows SharePoint Services-samhæft HTML ritil eins og Microsoft Office SharePoint Designer. Ef vandamálið er viðvarandi, samband vefþjóninn kerfisstjóra.

Ég kennt viðskiptavinur (ekki átta sig eins og enn, að það var mér að kenna á þessum tímapunkti) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Verið darned varkár þegar að vinna með ItemStyle.xsl (og eitthvað af alþjóðlegum XSL skrá) — brjóta þá snertir marga artifacts í the staður safn.

<endir />