Paano Magpadala ng isang email mula sa WebPart sa Moss 2007

Hi Devs,
Ang mga sumusunod ay mga piraso ng code na magpadala ng E-mail mula sa webpart.

paggamit ng System;
gamit System.Collections.Generic;
gamit System.ComponentModel;
gamit System.Text;
gamit System.Web;
gamit System.Web.UI;
gamit System.Web.UI.WebControls;
gamit System.Collections.ObjectModel;
gamit Microsoft.SharePoint.Utilities;
gamit Microsoft.SharePoint;
gamit System.Data;
gamit System.Collections;
namespace SendMail
{
pampublikong klase SendMail : Microsoft.SharePoint.WebPartPages.WebPart
{
pribadong textbox txtTo;
pribadong btnSendMail Pindutan;
protected override void CreateChildControls()
{
txtTo = new TextBox();
this.Controls.Add(txtTo);
btnSendMail = new Button();
btnSendMail.Text = “Magpadala ng Email”;
btnSendMail.Click = bagong EventHandler(SendMail_Click);
this.Controls.Add(btnSendMail);
}
walang bisa SendMail_Click(Ang nagpadala na bagay, EventArgs e)
{
SPSite _site = bagong SPSite(HttpContext.Current.Request.Url.ToString());
_web SPWeb = _site.OpenWeb();
_web.AllowUnsafeUpdates = true;
SPUtility.SendEmail(_web, hindi totoo, hindi totoo, txtTo.Text, “Pagsubok ng Email”, “Text Katawan ng Mensahe”);
_web.Dispose();
_site.Dispose();
}
}
}

Lumikha ng WebPart at iparehistro ito bilang SafeControl

Lumot 2007 Pagpepresyo & Ay nagkakahalaga ng Impormasyon

Ako ang pinagsama-sama ang ilang mga link mula sa Microsoft para sa Moss 2007 Ay nagkakahalaga ng Produkto.

Microsoft Office SharePoint Server 2007 at Kaugnay na Technologies pagpepresyo

Microsoft Office SharePoint Server 2007 paghahambing ng mga produkto ng pag-download

2007 Pagpepresyo sistema ng Microsoft Office at mag-upgrade ng impormasyon

Paano upang Itago ang Quick Launch sa Moss 2007

Gusto mo bang itago ang iyong quick launch bar sa Moss 2007
Mayroong dalawang paraan upang itago ang quick launch bar
1. Maaari mong i-edit nang direkta sa CSS
2. Pagdaragdag ng Mga nakatagong editor ng nilalaman webpart

Magdagdag ng bagong editor webpart nilalaman
I-click ang Pinagmulan Editor sa ToolPane
-paste ang code sa editor webpart nilalaman sa ibaba
[estilo]
.ms-quicklaunch
{
display:wala;
}
.ms-navframe
{
display: wala;
}
[/estilo]
Paggamit “<" & ">” sa halip “[” & “]”
Itakda ang Nakatagong Ari-arian sa True sa ilalim ng seksyong layout sa ToolPane.
Ngayon I-refresh ang Pahina……You Quick Launch Bar is Gone 🙂

Nagtatanghal sa ang humuhubog sa Hinaharap gawaan

Iniharap ko ang Demo sa Architecting ibinahagi sa pamamagitan ng mga application gamit Grid Arkitektura sa Accenture humuhubog sa Hinaharap workshop. Ito ay ang aking ikalawang pagtatanghal sa Accenture sa paghugis ng Hinaharap.

Paano upang pilitin Moss 2007 Timer ng Trabaho sa Ipatupad

Gamitin ang Sumusunod na stadm command upang pilitin ang mga trabaho sa mga trabaho timer upang maisagawa.
Hindi mo na kailangang maghintay para sa mga agwat upang maisagawa ang timerjobs.
stsadm.exe -o execadmsvcjobs

Lumot 2007 Palitan ang pangalan ng Web Application Pangalan

Gusto kong ibahagi ang kung paano upang pangalanang muli ang pangalan ng web application sa command line pamamahala ng Moss 2007 gamit STSADM Command.

Palaugnayan:
stsadm -o Renameweb -url -newname

Halimbawa:
Stsadm-o renameweb-url http://localhost / oldname-newname newname

Ang itaas na utos ay papangalanang muli ang mga web application mula oldname sa ang newname.

Commerce Server 2007 Pagsasama sa Moss 2007

MOSS has many inbuilt features. The scope of this POC is to integrate Commerce Server 2007 with MOSS 2007 to provide Portal Integrated e-Commerce Application

Configuring MOSS 2007 to Use the Commerce Server Membership Provider As The Basis For User Authentication

The primary tasks are to make the Central Administration and Portal sites hand-shake with Commerce Server. This needs to be done by modifying the appropriate Web.config files for these sites. By adding the Commerce Server and httpModules sections, the SharePoint Central Administration site and the Portal site will be able to create the necessary CommerceContext object. The CommerceContext object enables the Commerce Server Membership Provider to be initialized correctly, and also enables Web parts and pages in the portal to use the CommerceContext object to access Commerce Server resources such as the Product Catalog.
The UpmMembership Provider extends the Membership framework offered by ASP.Net to accommodate the use of the ASP.Net Login Controls and authenticate against Commerce Server Profiles.

Update the Web.config for MOSS Central Administration and in Portal site with below sections to avail Commerce Server data and services in MOSS

  • Commerce Server Section Group
  • Commerce Server Group
  • Http Modules
  • Assemblies
  • Membership Provider
  • Profile Section

o Determine which Web.config file is used for the SharePoint Central Administration site and which is used for the Portal site. Use the Home Directory tab in IIS Manager to determine the appropriate path of the Web.config file for each site.

o Use the Web.config file that was previously created for the Commerce Server C SharpSite as the source for the text to copy in the following instructions:

Please follow the below steps to modify the web.config file of SharePoint administration site.

Step 1: Adding Commerce Server Section Group
Copy the Commerce [sectionGroup] sa [configSections] and paste it after the [System.Workflow.ComponentModel.WorkflowCompiler] section group.
[sectionGroup name=”CommerceServer”]
[section name=”application” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceApplicationSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”authentication” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceAuthenticationSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”pipelines” type=”Microsoft.CommerceServer.Runtime.Configuration.CommercePipelineSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”caches” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceCacheSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”messageManager” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceMessageManagerSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”catalog” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceCatalogSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”orders” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceOrdersSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”profiles” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceProfilesSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”contentSelection” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceContentSelectionSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”commerceEvent” type=”Microsoft.CommerceServer.Runtime.Configuration.EventLoggerConfigurationHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”expressions” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceExpressionSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[/sectionGroup]
Step 2: Adding Commerce Server Group
§ Copy the [CommerceServer] section and paste it after the [SharePoint] section, just before the [system.web] section.

[CommerceServer]
[application siteName=”CDevSite” debugLevel=”Production”/]
[pipelines][/pipelines]
[expressions schema=”Auto”/]
[caches]
[cache name=”Advertising” type=”Advertising” refreshInterval=”900″ retryInterval=”30″/]
[cache name=”Discounts” type=”Discounts” refreshInterval=”0″ retryInterval=”30″/]
[cache name=”ShippingManagerCache” type=”Shipping” loaderProgId=”Commerce.ShippingMethodCache” refreshInterval=”0″ retryInterval=”30″/]
[cache name=”PaymentMethodCache” type=”Payment”/]
[cache name=”OrdersConfigurationCache” type=”OrdersConfiguration”/]
[/caches]
[messageManager]
[cultures default=”en-US” baseName=”CommerceMessageManager” assembly=”CommerceMessageManager”]
[culture id=”en-US”/]
[culture id=”fr-fr”/]
[culture id=”ja-JP”/]
[culture id=”de-DE”/]
[/cultures]
[resources]
[resource id=”pur_badsku”/]
[resource id=”pur_badplacedprice”/]
[resource id=”pur_discount_changed”/]
[resource id=”pur_discount_removed”/]
[resource id=”pur_noitems”/]
[resource id=”pur_badshipping”/]
[resource id=”pur_badhandling”/]
[resource id=”pur_badtax”/]
[resource id=”pur_badcc”/]
[resource id=”pur_badpayment”/]
[resource id=”pur_badverify”/]
[resource id=”pur_out_of_stock”/]
[resource id=”unknown_shipping_method”/]
[/resources]
[/messageManager]
[orders honorStatus=”totoo” newOrderStatus=”NewOrder” sqlCommandTimeoutSeconds=”60″ sqlLongRunningCommandTimeoutSeconds=”28800″]
[addressMap]
[profileDefinition name=”Tirahan”/]
[property from=”GeneralInfo.address_id” to=”OrderAddressId”/]
[property from=”GeneralInfo.first_name” to=”FIRSTNAME”/]
[property from=”GeneralInfo.last_name” to=”LastName”/]
[property from=”GeneralInfo.address_line1″ to=”Line1″/]
[property from=”GeneralInfo.address_line2″ to=”Line2″/]
[property from=”GeneralInfo.city” to=”City”/]
[property from=”GeneralInfo.region_code” to=”RegionCode”/]
[property from=”GeneralInfo.postal_code” to=”PostalCode”/]
[property from=”GeneralInfo.country_name” to=”CountryName”/]
[property from=”GeneralInfo.region_name” to=”State”/]
[property from=”GeneralInfo.tel_number” to=”DaytimePhoneNumber”/]
[/addressMap]
[Types]
[Type Key=”Basket” UserTypeName=”Basket” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PurchaseOrder” UserTypeName=”PurchaseOrder” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderTemplate” UserTypeName=”OrderTemplate” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderForm” UserTypeName=”OrderForm” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”LineItem” UserTypeName=”LineItem” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”Shipment” UserTypeName=”Shipment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”Payment” UserTypeName=”Payment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”CreditCardPayment” UserTypeName=”CreditCardPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”GiftCertificatePayment” UserTypeName=”GiftCertificatePayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PurchaseOrderPayment” UserTypeName=”PurchaseOrderPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”CashCardPayment” UserTypeName=”CashCardPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderAddress” UserTypeName=”OrderAddress” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”DiscountApplicationRecord” UserTypeName=”DiscountApplicationRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”ShippingDiscountRecord” UserTypeName=”ShippingDiscountRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PromoCodeRecord” UserTypeName=”PromoCodeRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[/Types]
[Limits OrderFormsPerOrderGroup=”5″ PromoCodeRecordsPerOrderForm=”10″ PromoCodesPerOrderForm=”10″ LineItemsPerOrderForm=”40″ OrderTemplatesPerUser=”10″ PaymentsPerOrderForm=”10″ ShipmentsPerOrderForm=”40″ BasketsPerUser=”15″ OrderAddressesPerOrderGroup=”10″/]
[MappingFiles PipelineMappingFilename=”OrderPipelineMappings.xml” StorageMappingFilename=”OrderObjectMappings.xml”/]
[SerializationBindings]
[SerializationBinding OldType=”Microsoft.CommerceServer.Runtime.Orders.LineItem , Microsoft.CommerceServer.Runtime ,Version=6.0.1.0,Culture=neutral, PublicKeyToken=31bf3856ad364e35″ NewType=”Microsoft.CommerceServer.Runtime.Orders.LineItem, Microsoft.CommerceServer.Runtime,Version=6.0.1.0,Culture=neutral, PublicKeyToken=31bf3856ad364e35″/]
[/SerializationBindings]
[/orders]
[commerceEvent]
[add className=”Microsoft.CommerceServer.Runtime.AddItemToBasketEvent” id =”AddItemToBasket”/]
[add className=”Microsoft.CommerceServer.Runtime.RemoveItemFromBasketEvent” id =”RemoveItemFromBasket”/]
[add className=”Microsoft.CommerceServer.Runtime.SubmitOrderEvent” id =”SubmitOrder” loggingEnabled=”totoo”/]
[/commerceEvent]
[/CommerceServer]
Step 3: Adding “CommerceApplication” sa “httpModules” Section
§ Copy the Commerce HTTP Modules to the end of the [httpModules] section.
[add name=”CommerceApplication” type=”Microsoft.CommerceServer.Runtime.CommerceApplicationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceAuthentication” type=”Microsoft.CommerceServer.Runtime.CommerceAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceOrder” type=”Microsoft.CommerceServer.Runtime.Orders.CommerceOrderModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceCatalog” type=”Microsoft.CommerceServer.Runtime.Catalog.CommerceCatalogModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceProfile” type=”Microsoft.CommerceServer.Runtime.Profiles.CommerceProfileModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceExpressionEvaluator” type=”Microsoft.CommerceServer.Runtime.Targeting.CommerceExpressionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceCache” type=”Microsoft.CommerceServer.Runtime.Caching.CommerceCacheModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceContentSelection” type=”Microsoft.CommerceServer.Runtime.Targeting.CommerceContentSelectionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/][add name=”CommerceDataWarehouseAuthenticationModule” type=”Microsoft.CommerceServer.Runtime.CommerceDataWarehouseAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″/]Remove or comment out the Commerce Server Authentication Module. This module is not required because ASP.NET Forms Authentication will be used for all authentications.
Step 4: Adding “Commerce Server” AssembliesCopy the commerce server assembly information from CSharpSite web.config and paste it in the [assemblies] tag in the Central Administration site’s web.config as below:
[assemblies]
[add assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31bf3856ad364e35″ /]
[add assembly=”Microsoft.CommerceServer.Catalog, Version=6.0.1.0, Kultura = neutral, PublicKeyToken=31BF3856AD364E35″ /][/assemblies]

Step 5: Configure Central Administration to recognize Commerce Server Membership
Copy the below code snippet to [system.web] section of the Web.config file for the Central Administration. Tala: Paste it before the closing [/system.web].
[membership defaultProvider=”UpmMembershipProvider”]
[providers]
[clear /]
[add applicationName=”CSharpSite ”
enablePasswordRetrieval=”hindi totoo”
enablePasswordReset=”totoo”
requiresQuestionAndAnswer=”totoo”
requiresUniqueEmail=”totoo”
enableCreateDate=”totoo”
enableEmailAddress=”totoo”
enableLastLoginDate=”totoo”
profileDefinition=”UserObject”
passwordFormat=”Hashed”
name=”UpmMembershipProvider”
type=”Microsoft.CommerceServer.Runtime.Profiles.UpmMembershipProvider”/]
[/providers]
[/membership]

Step 6: Configuring the Commerce Server Profiles section

This section contains settings which configure the functionality of profiles and catalog sets. Ang [userProfile] node resides in the [CommerceServer][profiles] node in the web.config.
Uncomment the profiles section in [commerceserver] node.

[userProfile
profileDefinition=”UserObject”
userIdProperty=”GeneralInfo.email_address”
organizationIdProperty=”AccountInfo.org_id”
catalogSetIdProperty=”AccountInfo.user_catalog_set”
userIdSource = “ASP.NET”
userIdKey = “GeneralInfo.email_address”
userIdTarget = “GeneralInfo.user_id”
/]
[organizationProfile
profileDefintion=”Organization”
organizationIdProperty=”GeneralInfo.org_id”
catalogSetIdProperty=”GeneralInfo.org_catalog_set”
/]

Step 7: Adding Users in the Central AdministrationLocate Central Administration, Application Pamamahala ng, Authentication Providers, Default zone entry. Make sure that you have the PortalSite Web Application selected in the drop-down list.

o Click Forms.

o Change the Membership Provider Name to UpmMembershipProvider. This should match the name that is in the membership section of the Web.config file.Locate Central Administration, Application Pamamahala ng, and Policy for Web Application. Make sure that you have selected the Portal Web Application.

o Click Add Users.

o Select Default zone, and then click Next.

o Type the e-mail address of the user that you added previously by using the Commerce Server Customer and Orders Manager, and then click Check User.

o If the user name is successfully recognized, it will be underlined. Select Full control, and then select Finish.

o If the user name is not recognized, run a SQL Server trace on the Commerce Server Profiles database to make sure that the queries are running against the database. Bukod pa rito, make sure that the entry for the provider is in the Web.config file for Central Administration, and look for errors in the event log.

Step 8: Copy the following XML files from the CSharpSite (IIS Virtual Directory) to the root folder of the Central Administration site:

o OrderObjectMappings.xml
o OrderPipelineMappings.xml

Run Central Administration to make sure that these changes were made correctly. If errors occur, check the Web.config file for syntax issues.Even if the page displays correctly, check the event log. Some permissions errors may be hidden.

Configure the MOSS portal to use the Commerce Server Membership provider:
Step 1: Follow the above 6 steps to configure Portal site for Commerce Server.

Step 2: Comment out the existing [authentication], [identity], at [authorization] sections. This will disable the default Windows authentication and authorization.

Step 3: Copy the below configuration settings contents to the Web.config file for the Portal site. Paste this after the previous sections that you just commented out. This sets up the site for Forms Authentication and denies anonymous access.

[authentication mode=”Mga Form”]
[forms loginUrl=”/_layouts/login.aspx” name=”.ASPXFORMSAUTH” /]
[/authentication]
[authorization]
[deny users=”?” /][/authorization] View the Portal site in a Web browser. You should be redirected to the logon page. Log on and use the user credentials that you added by using the Customer and Orders Manager.

Step 4: Copy the following XML files from the CSharpSite (IIS Virtual Directory) to the root folder of the Portal site:

o OrderObjectMappings.xml
o OrderPipelineMappings.xml

Step 5: Restart the IIS

Step 6: Run the Portal site and look for errors.

[Tala : I am not able to Post scripts tag in here replace all “[” & “]” with “<" & ">“

Libreng Microsoft Pindutin E-Books Alok para sa LINQ,ASP.Net,Silverlight

Ang sumusunod na E-Books maaaring ma-download mula sa Microsoft Press Site.

  • Ipinapakilala ang Microsoft LINQ
    sa pamamagitan ng Paul Pialorsi at Marco Russo
  • Ipinapakilala ang Microsoft ASP.NET AJAX
    sa pamamagitan ng Dino Esposito
  • Ipinapakilala ang Microsoft Silverlight 1.0
    sa pamamagitan ng Laurence Moroney

    http://csna01.libredigital.com

    Mag-login sa site gamit ang iyong pasaporte / Hotmail id at I-download ang e-Books para sa libreng.

Bill Gates Last Day sa Microsoft

Ibinigay ng Bill Gates ang kanyang huling pangunahing tono sa Ces(Consumer Electronic Ipakita) sa huling Vegas.

you can find his full keynote in Microsoft CES

Content Approval Workflow sa lumot 2007

Sa lumot 2007 Approval workflow ay magagamit sa labas ng kahon mismo. Basta kailangan namin upang isaayos ang tanging ilang hakbang pagkatapos ay kami ay handa na sa proseso ng pag-apruba.

Kung ang pag-apruba ng workflow ay isinaayos dokumento ay makikita lamang sa mga kontribyutor at sa mga Approver.

Hakbang sa Itakda ang daloy ng trabaho sa pag-apruba ng Nilalaman

Buksan ang Document Library
I-click ang Mga Setting -> Mga setting ng Dokumento Library


Sa Document Setting ng Library sa ilalim ng Pahintulot at Pamamahala ng Mag-click Workflow Setting

Document Setting ng Library -> [Pahintulot at Pamamahala] Workflow Management

Sa lumot 2007 ito ay may ilang prebuilt workflow mga template para sa mga sumusunod workflows

  • Pagpapatibay
  • Mangolekta ng Feedback
  • Mangolekta ng lagda
  • Disposisyon Approval
  • Tatlong Estado

Ngayon Piliin ang Approval Workflow at bigyan ang mga natatanging pangalan para sa mga halimbawa ng workflow.
Piliin ang Umiiral Task List Pangalan o lumikha ng bagong Task List para sa daloy ng trabahong pag-apruba.
Piliin ang Umiiral na History o lumikha ng bagong workflow kasaysayan upang mapanatili ang daloy ng trabaho sa kasaysayan.
Sa ilalim ng Start mga opsyon maaari mong tukuyin kung paano ang daloy ng trabaho na ito ay maaaring nagsimula.

· Payagan ang daloy ng trabaho na maging mano-mano na nagsimula sa pamamagitan ng isang napatunayang gumagamit ng I-edit ang mga Pahintulot Item
· Simulan ang daloy ng trabahong ito kapag ang isang item ay nilikha
· Simulan ang daloy ng trabahong ito kapag ang isang item ay nagbago

Kung pinili mo ang "magsimula sa daloy ng trabahong kapag ang isang item ay nilikha" ito ay awtomatikong magsisimula kapag ang daloy ng trabaho sa mga bagong bagay ay idinagdag sa library dokumento.

Kung pinili mo ang "magsimula sa daloy ng trabahong kapag ang isang item ay nagbago" awtomatikong ito ay restart ang daloy ng trabaho kapag ang mga bagay sa aklatan dokumento ay binago.

Sa ilalim ng workflow gawain
Kung pinili mo ang Magtalaga ng Gawain sa "Lahat ng mga kalahok sabay na" Ito ay lumikha ng mga gawain para sa lahat ng kalahok sa parehong oras. Ang daloy ng trabaho ay nakumpleto na lamang matapos ang pag-apruba ng lahat approvers.

Kung pinili mo ang Magtalaga ng Gawain sa "One kalahok sa isang panahon" Ito ay sundin ang mga sequence ng mga aktibidad sa unang workflow gawain ay nilikha sa ang unang user at sabay nito na inaprubahan lamang pagkatapos ay ilipat ito sa susunod ng Approver.

Kung ito ay kinakailangan na maaari mong itakda ang petsa para sa mga daloy ng trabaho.
Ang daloy ng trabaho sa katayuan maaari din na masabihan na iba sa mga kalahok ng daloy ng trabaho sa pamamagitan ng pagbibigay ng pangalan sa ipaalam sa iba haligi.

Kami ay ang paglikha ng workflow para sa Nilalaman Approval. Kaya huwag kalimutan ang check ang option na "I-update ang katayuan ng pagpapahintulot (gamitin ang daloy ng trabaho sa control apruba ng nilalaman)"

Ngayon mo matagumpay na nalikha approval workflow.

Ikaw ay may upang paganahin ang mga nilalaman ng pag-apruba sa library dokumento pagkatapos lamang ito rendahan ang ibang mga gumagamit na ma-access ito.

Kapag pinagana mo apruba ng nilalaman na dokumento ay makikita lamang sa mga kontribyutor / may-akda at Approver, hindi na ito ay makikita ng iba pang mga gumagamit sa dokumento aklatan.

Open Settings -> Document Setting ng Library
Sa ilalim ng Pangkalahatang mga Setting -> versioning Setting
Nangangailangan Content Approval para Submitted Item? Piliin ang Oo
At I-click ang OK upang I-save ang mga Setting.

Ngayon Buksan ang Document Library at mag-upload ng mga Dokumento

Ngayon ang dokumento ay na-upload na mga Dokumento Library

Kung pag-login gamit ang ilang iba pang mga katibayan ng gumagamit (hindi isang Approver / kontribyutor). Ang dokumento ay ipapakita sa library dokumento.

Kung sa tingin mo ang post na ito ay tumutulong sa iyo na lumikha ng workflow para apruba ng nilalaman. Mangyaring iwan ang iyong mga mahahalagang komento.