Arkivji ta 'Kull Xahar: Diċembru 2007

Thinking About Prodotti Kummerċjali

2 tweġibiet

I imqiegħed Proġett estensjonijiet Designer SharePoint up fuq CodePlex aktar kmieni din is-sena u anki jekk huwa verament pjuttost limitata fl-ambitu, Jiena nistma li huwa kien jitniżżel minn 40 li 60 (possibilment anke 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, li jistgħu jsarrfu ammont goodly ta 'birra 🙂

Isfond tiegħi huwa fil-fatt ħafna aktar fl-iżvilupp tal-prodott u naf dak li huwa meħtieġ biex prodott top-talja, bħala kuntrarju għal proġett passatemp CodePlex, to market. In my ħajja tal-passat, I kien responsabbli għall-prodott R&D for all software products. The difference between then and now is that I’m a consultant now working for an (eċċellenti) ditta ta 'konsultazzjoni (Conchango). Preċedentement, I kellha kumpannija sħiħa lura lili u quddiem lili, selling and supporting the products we brought to market. Illum, I d jkun waħdu.

I jkollhom diversi ideat prodott fil-moħħ, 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 għal liċenzja iżviluppatur bla limitu u $500 per production web front end. I think I would also give away the source code.

Jekk għandek ħsibijiet jew esperjenzi li int lesti li jaqsmu, jekk jogħġbok leave kumment jew email lili direttament. I’d like to hear opinions like:

  • Huwa kollha utli?
  • Suġġerimenti prattiċi għall-marketing, ġbir ta 'flus, distribuzzjoni.
  • Ipprezzar.
  • Appoġġ.
  • Kwalunkwe kumment ieħor li tixtieq li jħallu.

It’s "easy" biex joħorġu b'ideat prodott u biex jimplimentawhom, though many dozens of hours of work are required. The other stuff is not as easy for me.

</aħħar>

Ħadd filgħodu Funny: “Ġesù Must Die”

1 Irrispondi

Aħna mixtrija tagħna ewwel (u biss) "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 diversi jiem għadda before life returned to normal. Just before Floyd struck, aħna għamlet offerta għal Volvo użati 850 GL u wara Floyd laqat, saq dar.

It was our first car with a CD player. Like most new car owners, aħna marru CD crazy ftit, 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. Fil-każ tagħna, kien Ġesù Kristu Superstar.

Wieħed mill- (ħafna) biċċiet brillanti f'dak blat opra hija kantata minn-tipi reliġjużi istabbiliment, mmexxija mill 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, għandu die, għandu die, this Jesus must die". You hear that refrain a lot in that piece.

Fil-ħin, 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, tfittex permezz tal-posta u kollha walk-in-the-bieb tas-soltu tiegħi għalf u I f'daqqa jirrealizzaw li hu biss qal, mhux verament kant: "Jesus must die, għandu 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 — probabbilment l-aħħar data play ma 'dak ħabib baby.

Aħna jinġibed li CD mill-Volvo wara li 🙂

</aħħar>

Google Did Aċċetta My Live Spaces Blog Into-Programm AdSense

7 tweġibiet

UPDATE: Mill- 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.

Din mhix post SharePoint, iżda jistgħu jkunu ta 'interess bloggers ġeneralment.

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. Madankollu, I kien reċentement aċċettat fil-programm għall-ispazji ħajjin tiegħi blog, sabiex il-politika tkun jew inbidlet jew Google miċħuda tagħha għal xi raġuni oħra.

Of course, I ma tara l-ebda mod ovvju biex jintegraw Google AdSense fl-ispazju ħajjin tiegħi, imma hija bidu 🙂

</aħħar>

Master Implimentazzjoni / Relazzjonijiet dettall użu ta 'listi Custom

5 tweġibiet

Utenti forum spiss bħala mistoqsijiet bħal din:

> Hello,
>
> Jekk jogħġbok għidli jekk hemmx xi possibbiltajiet biex tinbena lista dwana ma
> kaptan u dettall tip (bħal fatturi) mingħajr l-użu InfoPath.
>

SharePoint jipprovdi wħud mill-karatteristiċi kaxxa li jappoġġjaw tipi ta 'ħtiġiet tan-negozju bħal dik.

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

Jużaw listi addizzjonali li jżommu klijent numri, numri tal-prodott, eċċ.

Uża parti kontenut tal-web query (fil MOSS biss) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) huwa wkoll disponibbli għall-naħa rappurtar ta 'dan.

Madankollu, 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:

  • Daqs tal lookup relatati listi 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 oġġetti, that’s going to be a problem. The lookup control does not page through those items. Minflok, 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. Per eżempju, 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. Stajt bil-miktub dwar dan hawn. You can’t implement cascading drop-downs, jippermettu kondizzjonalment / jiskonnettja oqsma, eċċ.
  • 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. Per eżempju, SharePoint jippermettilek li toħloq żewġ listi tad-dwana, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Imbagħad, you can delete the customer from the list. Barra mill-kaxxa, there is no way to prevent this. To solve this kind of problem, inti normalment tuża handlers avveniment.

Dan jista 'jidher skoraġġanti, 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 tgħinna biex timla dawn il-lakuni permezz ta 'għodod bħall-:

  • Handlers Avveniment. Use them to enforce referential integrity.
  • Kolonni Custom: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering u l-karatteristiċi Ajax sabiex isiru sensittivi.
  • 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 hija karatteristika MOSS (mhux disponibbli fil WSS) and is challenging to configure.

  • Formola tal-web ASP.NET: Oħloq full-dehru forma AJAX-ppermettiet li juża l-mudell oġġett SharePoint u / jew servizzi tal-web għal-listi SharePoint lieva filwaqt li tipprovdi user interface ferm reattivi.

L-aħħar għażla tista 'tħossok bħal int tibda mill-bidu, iżda tikkunsidra l-fatt li l-pjattaforma SharePoint jibda inti off mal-karatteristiċi ewlenin li ġejjin:

  • Sigurtà mudell ma 'manutenzjoni.
  • Sistema menu mal-manutenzjoni.
  • "Master table" (I.E. listi tad-dwana) mas-sigurtà, mibnija fil-manutenzjoni u l-verifika.
  • Fittex.
  • Back jispiċċaw integrazzjoni għodod (BDC).

Jekk tibda bi proġett blank ġdid fl-istudjo viżwali, ikollok ħafna ta 'infrastruttura u plumbing biex jibnu qabel ikollok qrib għal dak offerti SharePoint.

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, jekk jogħġbok leave kumment.

</aħħar>

Tip Quick: Parti kontenut Web Mistoqsija, Lookup Valur Kolonna u XSL

3 tweġibiet

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

That column is of type "lookup".

I immodifikaw <CommonViewFields> u ItemStyle.xsl biex juru l-kolonna.

A sempliċi <XSL:valur tal tagħżel =…> prospetti lura valur intern li tinkludi data tal-posizzjoni ordinal, bħal:

1;#Miami

Biex tikseb il-valur tal-bniedem-friendly, użu XSL substring-wara, kif muri:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,"#")"></XSL:il-valur tal->

Uża din it-teknika meta inti taħdem ma 'valuri Lookup fil jittrasforma XSL u jeħtieġ li jiksbu l-valur tal-bniedem-friendly.

<aħħari />

Tags: , ,

SharePoint Beagle Diċembru Ħruġ Up & Live

Ħalli Risposta

Many of you know this already, but the December edition of SharePoint Beagle is live.

Every article is worth reading in my opinion.

I want to give a little extra bump to my colleague’s article (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 her blog while you’re at it.

Don’t forget to check out artiklu tiegħi kif ukoll 🙂 I kiteb dwar l-użu MOSS biex jgħinu dipartiment HR tamministra pożizzjonijiet miftuħa.

</aħħar>

MOSS jgħidlekx Me “Aċċess Denied” Edit Task Workflow, Imma I really do jkollhom aċċess

2 tweġibiet

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (I.E. kulħadd). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, jista jassenjaw il-ħidmiet lil nies.

I break permess għall-librerija forom u l-lista kompitu sabiex kwalunkwe utent awtentikat jistgħu joħolqu forom u taġġorna kompiti assenjati lilhom.

I test with my low-privileges test account.

Nista jimlew u tiffranka formola għal-librerija? –> IVA

Nista 'aċċess għall-kompitu minn link email? –> IVA

Nista tara link Edit kompitu workflow –> IVA

Nista ikklikkja fuq din ir-rabta? –> NO … Permess Denied.

Għaliex nista 'tara link edit li tiċħad me permess meta I ikklikkja fuqha? That’s not how it’s supposed to work…

I jgħaddu mill-konfigurazzjoni mill-ġdid tas-sigurtà, very closely. I do it again. Inqis tħassar din il-kariga minħabba I ovvjament ma jafu xejn dwar is-sigurtà.

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

Il-posters jidhru li jissuġġerixxu li l-att sempliċi ta 'jesporta l-fluss tax-xogħol għal platter drive se tiffissa kwistjoni tas-sigurtà MOSS? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 konspirazzjoni fejn Stan qed titlob Preznit tagħna, "Really?" over and over again.

Allura, xejn x'titlef, I nar up SPD, dritt ikklikkja fuq il-fluss tax-xogħol u tiffranka lill c tiegħi:\ 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?"

Oerhört, that solves my problem. I can edit the task.

Jiena hawnhekk jinnomina din l-workaround Workflow aktar stramba ta ' 2007.

</aħħar>

SharePoint Designer, Punt attwali “Encoded URL assoluta” u HTTPS

4 tweġibiet

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

immaġni

Safejn naf, there is no out of the box solution to this problem. If you need to use HTTPS, you have no out of the box option.

To solve it, create a custom action that provides a string replace function to use in your workflow. Alternatively, use a 3rd party tool such as the excellent package here: http://www.codeplex.com/spdwfextensions 🙂

</aħħar>

Quick u Easy: Iddetermina Intern Kolonna Isem ta 'Kolonna Sit

3 tweġibiet

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 jassumi li l-isem kolonna għall-użu fil- <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. Mill-inqas, 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" isem, 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. Iżda, 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>

</aħħar>

Beware Bidliet Breaking għall ItemStyle.xsl

Ħalli Risposta

I kien qed jaħdem mal ItemStyle.xsl biex jippersonalizzaw l-ħarsa ta 'kontenut Web Mistoqsija Parti u d-dritt dwar il-ħin ikla, 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, ndunat dan il-messaġġ li jidher fil-mazz ta 'postijiet:

Kapaċi li juru din it-Taqsima tal-Web. Biex troubleshoot l-problema, tiftaħ din il-paġna tal-Web fil-Windows Servizzi kompatibbli SharePoint HTML editur bħal Microsoft Office SharePoint Designer. Jekk il-problema tippersisti, ikkuntattja l-amministratur tiegħek Web server.

I ħtija tal-klijent (ma rrealizza li għadu li kien tort tiegħi f'dan il-punt) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Ikunu attenti meta darned jaħdmu ma ItemStyle.xsl (u kwalunkwe mill-fajls XSL globali) — jkissruhom taffettwa artifacts ħafna fil-ġbir sit.

<aħħari />