Nyaraka za kila mwezi: Desemba 2007

Kufikiri Kuhusu Bidhaa Commercial

Mimi kuweka SharePoint Designer upanuzi wa mradi hadi saa CodePlex mapema mwaka huu na hata ingawa ni kweli kabisa mdogo katika upeo, Mimi makisio kwamba imepakuliwa na 40 kwa 60 (pengine hata 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, ambayo inaweza kutafsiri katika kiasi mzuri ya bia 🙂

Background yangu ni kweli zaidi katika maendeleo ya bidhaa na mimi najua ni nini wanatakiwa kuleta bidhaa juu-notch, kinyume na mradi hobby CodePlex, to market. In my kipindi cha maisha, Mimi alikuwa na wajibu wa bidhaa R&D for all software products. The difference between then and now is that I’m a consultant now working for an (bora) kampuni ya ushauri (Conchango). Hapo awali, Mimi nilikuwa na kampuni nzima nyuma yangu na mbele yangu, selling and supporting the products we brought to market. Leo, Ningependa kuwa peke.

Nina mawazo kadhaa bidhaa katika akili, 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 kwa ukomo developer leseni na $500 per production web front end. I think I would also give away the source code.

Kama una mawazo au uzoefu kwamba uko tayari kushiriki, tafadhali kuacha maoni au email yangu moja kwa moja. I’d like to hear opinions like:

  • Je, ni vyema?
  • Vitendo mapendekezo kwa ajili ya masoko, kukusanya fedha, kusambaza.
  • Bei.
  • Kusaidia.
  • Maoni yoyote nyingine Ningependa kuondoka.

It’s "easy" kuja na mawazo ya bidhaa na kutekeleza yao, though many dozens of hours of work are required. The other stuff is not as easy for me.

</mwisho>

Tags technorati:

Sunday Morning Mapenzi: “Yesu Must Die”

Sisi kununuliwa kwanza wetu (na tu) "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 siku kadhaa kupita before life returned to normal. Just before Floyd struck, sisi alifanya kutoa kwa ajili ya Volvo kutumika 850 GL na baada Floyd akampiga, alimfukuza nyumbani.

It was our first car with a CD player. Like most new car owners, tulikwenda kidogo CD mambo, 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. Katika kesi yetu, ilikuwa ni Yesu Kristo Superstar.

Moja ya (wengi) vipande kipaji katika kwamba opera mwamba ni kuimba na aina ya uanzishwaji wa dini, wakiongozwa na Kayafa, 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, lazima kufa, lazima kufa, this Jesus must die". You hear that refrain a lot in that piece.

Wakati, 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, kutafuta njia ya barua na kawaida yangu kila kutembea-katika-mlango-stuff na mimi ghafla kutambua kwamba yeye tu kusema, si kweli kuimba: "Jesus must die, lazima kufa, 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 — pengine mwisho kucheza na tarehe na rafiki kwamba mtoto.

Sisi vunjwa kwamba CD kutoka Volvo baadaye 🙂

</mwisho>

Tags technorati: ,

Google Je Kubali yangu Nafasi Live Blog Ndani ya Adsense

UPDATE: Kama ya 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.

Hii si baada SharePoint, lakini inaweza kuwa ya riba kwa wanablogu ujumla.

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. Hata hivyo, Mimi nilikuwa hivi karibuni kukubaliwa katika mpango kwa ajili ya nafasi yangu ya kuishi blog, hivyo sera ina ama kubadilishwa au Google alikanusha yake kwa ajili ya baadhi ya sababu nyingine.

Bila shaka, Sioni njia yoyote dhahiri kuunganisha Google Adsense katika nafasi yangu ya kuishi, lakini huu ni mwanzo 🙂

</mwisho>

Tags technorati: ,

Utekelezaji wa Mwalimu / Undani Mahusiano Kutumia Orodha Desturi

Forum users frequently as questions like this:

> Hujambo,
>
> Tafadhali niambie kama kuna uwezekano wa kujenga orodha ya desturi na
> bwana na undani aina (kama ankara) without using InfoPath.
>

SharePoint hutoa baadhi ya nje ya makala sanduku kwamba msaada wa aina ya mahitaji ya biashara kama kwamba.

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

Use additional lists to maintain customer numbers, product numbers, nk.

Use a content query web part (in MOSS only) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) is also available for the reporting side of it.

Hata hivyo, 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:

  • Size of related lookup lists 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 vitu, that’s going to be a problem. The lookup control does not page through those items. Badala yake, 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. Kwa mfano, 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. Nimeandika kuhusu hili hapa. You can’t implement cascading drop-downs, masharti kuwawezesha / afya ya mashamba, nk.
  • 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. Kwa mfano, SharePoint inaruhusu kujenga orodha mbili desturi, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Kisha, you can delete the customer from the list. Nje ya boksi, there is no way to prevent this. To solve this kind of problem, ungependa kawaida kutumia handlers tukio.

Inaweza kuonekana hatarini, 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 unatuwezesha kujaza mapengo wale kutumia zana kama vile:

  • Event handlers. Use them to enforce referential integrity.
  • Desturi nguzo: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering na makala AJAX kuwafanya msikivu.
  • 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 ni hulka MOSS (si inapatikana katika WSS) and is challenging to configure.

  • ASP.NET mtandao fomu: Kuunda full-featured AJAX-enabled fomu kwamba anatumia kitu SharePoint mfano wa kuigwa na / au huduma za mtandao na orodha SharePoint kujiinua wakati kutoa msikivu sana user interface.

hatua ya mwisho inaweza kuhisi kama wewe ni kuanzia mwanzo, lakini kuzingatia ukweli kwamba jukwaa SharePoint kuanza wewe mbali na makala muhimu yafuatayo:

  • Usalama mfano wa kuigwa na matengenezo ya.
  • Mfumo menu na matengenezo ya.
  • "Master table" (i.e. desturi orodha) na usalama, kujengwa katika matengenezo na ukaguzi.
  • Kutafuta.
  • Nyuma mwisho zana ushirikiano (BDC).

Kama wewe kuanza na mradi mpya katika studio ya Visual tupu, una mengi ya miundombinu na mabomba ya kujenga kabla ya kupata karibu na nini SharePoint inatoa.

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, tafadhali acha maoni.

</mwisho>

Haraka Tip: Content Query Mtandao Sehemu ya, Luke Column Thamani na XSL

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

That column is of type "lookup".

Mimi tarehe <CommonViewFields> na ItemStyle.xsl kuonyesha safu.

rahisi <xsl:thamani ya kuchagua =…> anarudi nyuma thamani ya ndani kuwa ni pamoja na data nafasi makutano, kama vile:

1;#Miami

Kupata thamani ya binadamu ya kirafiki, kutumia XSL substring-baada ya, kama inavyoonekana:

<xsl:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></xsl:thamani ya>

Kutumia mbinu hii wakati wewe ni kufanya kazi na maadili lookup katika kuugeuza XSL na haja ya kupata thamani ya binadamu ya kirafiki.

<mwisho />

Tags technorati: , ,

SharePoint Beagle Desemba Suala Up & Kuishi

Wengi wa unajua hii tayari, lakini Desemba toleo la SharePoint Beagle ni kuishi.

Kila makala ni thamani ya kusoma kwa maoni yangu.

Mimi nataka kutoa ziada kidogo mapema kwa mwenzake yangu makala (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 yake blog wakati uko katika hilo.

Usisahau kuangalia nje yangu makala pamoja 🙂 niliandika kuhusu kutumia MOSS kusaidia idara HR kusimamia nafasi za wazi.

</mwisho>

MOSS Inaeleza Me “Upatikanaji Wanyimwa” kwa Hariri Task Workflow, Lakini mimi Kweli Je, Je Access

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. kila mtu). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, inaweza hawawajui kazi kwa watu.

I break permission for the forms library and task list so that any authenticated user can create forms and update their assigned tasks.

I test with my low-privileges test account.

Can I fill out and save a form to the library? –> YES

Can I access the task from an email link? –> YES

Can I see an Edit workflow task link –> YES

Can I click on that link? –> NO … Permission Denied.

Why can I see an edit link that denies me permission when I click on it? That’s not how it’s supposed to work…

I go through the security configuration again, very closely. I do it again. I consider deleting this post because I obviously don’t know anything about security.

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

The posters appear to be suggesting that the simple act of exporting the workflow to a drive platter will fix a MOSS security issue? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 conspiracy where Stan is asking our Preznit, "Really?" over and over again.

Hivyo, nothing to lose, I fire up SPD, right-click on the workflow and save it to my c:\ 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?"

Incredibly, that solves my problem. I can edit the task.

Mimi hili kuteua hii kuwa wengi Bizarre Workflow workaround ya 2007.

</mwisho>

Tags technorati:

SharePoint Designer, Sasa Item ya “Encoded Absolute URL” na HTTPS

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. Hata hivyo, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

picha

Mbali kama mimi najua, there is no out of the box solution to this problem. If you need to use HTTPS, wewe huna nje ya chaguo sanduku.

Kulitatua, create a custom action that provides a string replace function to use in your workflow. Alternatively, kutumia chama 3 chombo kama vile mfuko bora hapa: http://www.codeplex.com/spdwfextensions 🙂

</mwisho>

Tags technorati: ,

Haraka na Easy: Kuamua Ndani Column Jina la Column Site

UPDATE: Jeremy Thake ina blogged kuhusu hili na kuweka baadhi kanuni kwa ajili ya maombi console kwamba inaonyesha majina ya ndani.

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", Mimi kudhani kwamba jina safu ya kutumia katika <CommonViewFields> is "Due_x0020_Date".

Vibaya!

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

Jinsi gani mimi kupata? I re-read Heather Suleimani blog kuingia kwenye kubadilisha 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" jina, Nilitaka kuongeza mwingine kwa shamba <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Mimi nilidhani, 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.

Ziada ncha: Wakati mimi alikuwa anafanya kazi na CQWP, kama mimi aliongeza mbaya ndani kwa jina <CommonViewFields>, the CQWP would tell me that the query had returned no results. Lakini, kama mimi aliongeza aina data kwa jina shamba, 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, lakini wakati nilijaribu kuonyesha thamani yake, I would always get a blank.

Hii si kufunika kosa:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Hii hakuwa mask kosa:

<CommonViewFields>Due_x0020_Date,DATETIME;</CommonViewfields>

</mwisho>

Jihadharini Mabadiliko Breaking kwa ItemStyle.xsl

Nilikuwa kazi na ItemStyle.xsl Customize ya kuangalia ya Sehemu ya Content Query Mtandao na haki juu ya wakati chakula cha mchana, 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, niliona ujumbe huu kuonekana katika rundo la maeneo:

Haiwezi kuonyesha Sehemu hii Mtandao. Troubleshoot tatizo, kufungua ukurasa huu mtandao katika Windows SharePoint mhariri Huduma-sambamba HTML kama vile Microsoft Office SharePoint Designer. Kama tatizo litaendelea, kuwasiliana yako Web server msimamizi.

Ninamlaumu mteja (si kutambua kama bado kwamba ilikuwa ni kosa langu katika hatua hii) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Kuwa darned makini wakati wa kufanya kazi na ItemStyle.xsl (na yoyote ya mafaili kimataifa XSL) — kuvunja yao huathiri mabaki wengi katika ukusanyaji tovuti.

<mwisho />