<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Заметки с полей : .Net</title><link>http://blogs.technet.com/valmond/archive/tags/.Net/default.aspx</link><description>Tags: .Net</description><dc:language>ru-RU</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Заметка о разработке. Транзакции и SharePoint</title><link>http://blogs.technet.com/valmond/archive/2006/11/26/sharepoint.aspx</link><pubDate>Sun, 26 Nov 2006 03:11:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:530683</guid><dc:creator>valmond</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/valmond/comments/530683.aspx</comments><wfw:commentRss>http://blogs.technet.com/valmond/commentrss.aspx?PostID=530683</wfw:commentRss><wfw:comment>http://blogs.technet.com/valmond/rsscomments.aspx?PostID=530683</wfw:comment><description>&lt;P&gt;Иногда сталкиваешься с ситуацией, когда необходимо выполнить в одной транзакции несколько действий с объектной моделью SharePoint.&lt;BR&gt;К сожалению официального решения для этой проблемы не существует, но зато существует один обходной путь, который не решает всех проблем, но в некоторых ситуациях помогает. &lt;/P&gt;
&lt;P&gt;Итак...если бы весь код SharePoint был managet, то можно было бы использовать TransactionScope, но т.к. по историческим причинам в SharePoint-е всех версий живет какое-то количество unmanaget кода, то выход можно усмотреть в облегченных COM+ транзакциях. &lt;/P&gt;
&lt;P&gt;&lt;SPAN style="COLOR: #1f497d"&gt;ServiceConfig Sc = new ServiceConfig();&lt;BR&gt;Sc.Transaction = TransactionOptions.RequiresNew;&lt;BR&gt;Sc.IsolationLevel = TransactionIsolationLevel.ReadCommited;&lt;BR&gt;///set some other Sc properties &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="COLOR: #1f497d"&gt;ServiceDomain.Enter(Sc); &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="COLOR: #1f497d"&gt;Try{&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SPSite site = new SPSite("…..");&amp;nbsp; &lt;STRONG&gt;Важно!!! Не брать из текущего контекста&lt;/STRONG&gt;&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ///do something with SharePoint OM&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ContextUtil.EnableCommit();&lt;BR&gt;}catch{&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; …&lt;BR&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ContextUtil.SetAbort();&lt;BR&gt;} &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="COLOR: #1f497d"&gt;ServiceDomain.Leave(); &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Проблема, которая может всплыть при таком решении достаточно очевидна. Это deadlock. &lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=530683" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/valmond/archive/tags/WSSv3_2F00_MOSS/default.aspx">WSSv3/MOSS</category><category domain="http://blogs.technet.com/valmond/archive/tags/.Net/default.aspx">.Net</category><category domain="http://blogs.technet.com/valmond/archive/tags/SharePoint/default.aspx">SharePoint</category></item><item><title>Visual Studio 2005 Tools for Office Second Edition</title><link>http://blogs.technet.com/valmond/archive/2006/11/09/visual-studio-2005-tools-for-office-second-edition.aspx</link><pubDate>Thu, 09 Nov 2006 10:26:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:510278</guid><dc:creator>valmond</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/valmond/comments/510278.aspx</comments><wfw:commentRss>http://blogs.technet.com/valmond/commentrss.aspx?PostID=510278</wfw:commentRss><wfw:comment>http://blogs.technet.com/valmond/rsscomments.aspx?PostID=510278</wfw:comment><description>&lt;P&gt;Вышла новая версия VSTO&lt;/P&gt;
&lt;P&gt;Кратко по функциональности&lt;/P&gt;
&lt;UL style="MARGIN: 5px 10px -70px 15px"&gt;
&lt;LI&gt;Application-level add-in support for the most popular 2007 Office System applications including Outlook, Excel, Word, &lt;STRONG&gt;PowerPoint&lt;/STRONG&gt;, InfoPath, and &lt;STRONG&gt;Visio&lt;/STRONG&gt;, and provides safe loading/unloading and easy management of managed add-ins. 
&lt;LI&gt;Design-time and runtime support for key 2007 Office System features such as the Ribbon, Custom Task Panes, and Outlook forms regions. 
&lt;LI&gt;Design-time support for InfoPath 2007 form templates. 
&lt;LI&gt;Maintainability and compatibility assurances. VSTO 2005 SE ensures that the applications customers have built on Office 2003 with VSTO 2005 continue to run with 2007 Office system. 
&lt;LI&gt;The ability to run in Visual Studio 2005 Professional, in addition to those Visual Studio versions already supported, including all of the MSDN subscriptions and Visual Studio Team System family of products. 
&lt;LI&gt;Expanded application-level add-in support for these Office 2003 Standard and Professional applications: Word, Excel, Outlook, PowerPoint and Visio. &lt;/LI&gt;&lt;/UL&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Также &lt;A class="" href="http://wm.microsoft.com/ms/msdn/Office/VSTO2005SEIntro/VSTO2005SEIntro.wmv" target=_blank mce_href="http://wm.microsoft.com/ms/msdn/Office/VSTO2005SEIntro/VSTO2005SEIntro.wmv"&gt;выложили видео&lt;/A&gt; с демонстрацией нового функионала&lt;/P&gt;
&lt;P&gt;Подробнее о VSTO SE &lt;A class="" href="http://msdn.microsoft.com/office/tool/vsto/2005SE/default.aspx" mce_href="http://msdn.microsoft.com/office/tool/vsto/2005SE/default.aspx"&gt;тут&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A class="" href="http://www.microsoft.com/downloads/details.aspx?FamilyId=5E86CAB3-6FD6-4955-B979-E1676DB6B3CB&amp;amp;displaylang=en" mce_href="http://www.microsoft.com/downloads/details.aspx?FamilyId=5E86CAB3-6FD6-4955-B979-E1676DB6B3CB&amp;amp;displaylang=en"&gt;А вот страница для скачивания&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=510278" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/valmond/archive/tags/Office+12/default.aspx">Office 12</category><category domain="http://blogs.technet.com/valmond/archive/tags/.Net/default.aspx">.Net</category><category domain="http://blogs.technet.com/valmond/archive/tags/InfoPath/default.aspx">InfoPath</category></item><item><title>Вышел Visual Studio 2005 SP1 Beta</title><link>http://blogs.technet.com/valmond/archive/2006/09/26/459195.aspx</link><pubDate>Tue, 26 Sep 2006 22:23:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:459195</guid><dc:creator>valmond</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/valmond/comments/459195.aspx</comments><wfw:commentRss>http://blogs.technet.com/valmond/commentrss.aspx?PostID=459195</wfw:commentRss><wfw:comment>http://blogs.technet.com/valmond/rsscomments.aspx?PostID=459195</wfw:comment><description>&lt;P&gt;До 30 октября можно скачать SP1 Beta с &lt;A href="http://connect.microsoft.com/visualstudio"&gt;http://connect.microsoft.com/visualstudio&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Обновления касаются следующих продуктов&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"&gt;Visual Studio&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"&gt;Visual Studio Express&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"&gt;Team Foundation Service&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"&gt;
&lt;P&gt;&lt;STRONG&gt;Version Control, WorkItem Tracking and Datawarehouse performance/scale improvements&lt;/STRONG&gt; - the majority of these have come from our continued internal deployment.&amp;nbsp; You can read&amp;nbsp;one &lt;A href="http://blogs.msdn.com/bharry/archive/2006/09/26/772371.aspx"&gt;blog posts&lt;/A&gt;&amp;nbsp;for more detail on what kinds of things we've hit and addressed.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;"Extranet support"&lt;/STRONG&gt; - We implemented an ISAPI filter that will allow the intranet to use&amp;nbsp;NTLM and integrated auth&amp;nbsp;while the extra net uses basic auth.&amp;nbsp; This enables TFS to be more easily deployed in environments where people on the internet need to be able to access TFS without having VPN. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;WIT Custom Control support&lt;/STRONG&gt; - This is a cool&amp;nbsp;new feature.&amp;nbsp; It is a mechanism by which people can design work item forms that host custom controls.&amp;nbsp; The data behind the controls can either be persisted in WIT fields or elsewhere.&amp;nbsp; I'm hoping people go crazy with&amp;nbsp;it and build some&amp;nbsp;awesome custom controls. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Support for Office&amp;nbsp;2007 (Project and Excel - no Sharepoint&amp;nbsp;2007 support yet), Vista and the new WAP project support&lt;/STRONG&gt; - These were all things that were pretty far from shipping when we shipped so it was not possible to work out all the kinks (bugs on both sides).&amp;nbsp; Now that&amp;nbsp; they are much closer and more stable we've been able to make them work well.&amp;nbsp; Please don't try to install TFS with Sharepoint 2007 at this point - we know it will not work.&amp;nbsp; We are working on Sharepoint 2007 support for Orcas - it will not be in SP1.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Detailed Merge History&lt;/STRONG&gt; - We realized after we shipped V1 that we had not exposed all of the information from the server necessary to build all of the sophisticated change tracking tools we use internally that track the flow of changes through branches.&amp;nbsp; The server "summarized" merge history information too much and we could only approximate the information.&amp;nbsp; SP1 includes a new web service method and object model API that allows access to the detailed information.&amp;nbsp; The new API is called QueryMergesWithDetails on the SourceControl object.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Separating the SQL Analysis Services Server&lt;/STRONG&gt;&amp;nbsp;- Over time we've received a lot of feedback from people about supporting more flexible deployment topologies - Sharepoint on separate servers, SQL Named instances, Reporting services on separate servers and more.&amp;nbsp; SP1 has one small step in that direction by including the change necessary to support TFS using SQL Analysis Server installed on a separate machine.&amp;nbsp; A few of you noticed that some of our servers are configured that way in the dogfood deployment diagram I posted a while back.&amp;nbsp; Now you can do it yourself.&lt;/P&gt;
&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;/SPAN&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=459195" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/valmond/archive/tags/.Net/default.aspx">.Net</category></item><item><title>Managed код в InfoPath 2007</title><link>http://blogs.technet.com/valmond/archive/2006/08/20/448085.aspx</link><pubDate>Mon, 21 Aug 2006 00:06:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:448085</guid><dc:creator>valmond</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.technet.com/valmond/comments/448085.aspx</comments><wfw:commentRss>http://blogs.technet.com/valmond/commentrss.aspx?PostID=448085</wfw:commentRss><wfw:comment>http://blogs.technet.com/valmond/rsscomments.aspx?PostID=448085</wfw:comment><description>&lt;p&gt;Известный факт, что InfoPath 2003 требовал от формы Full Trust разрешений для того, чтобы форма могла содержать managed код. В InfoPath 2007 это ограничение снято, теперь вполне можно писать свой код на C# и при этом задавать уровень безопасности Domain (при этом правда, форма должна быть опубликована в зоне intranet). 
&lt;/p&gt;&lt;p&gt;Этот факт не может не радовать т.к. Full Trust накладывает на форму сильные ограничения в виде подписи сертификатом или в виде локальной установки, что в большинстве случаев сводит на нет все преимущества использования управляемого кода.&lt;/p&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=448085" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/valmond/archive/tags/.Net/default.aspx">.Net</category><category domain="http://blogs.technet.com/valmond/archive/tags/InfoPath/default.aspx">InfoPath</category></item></channel></rss>