Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is how I spit out .NET 1.1 versions compiled against WSSv2 API and .NET 2.0 compiled against WSSv3 assembly. It will work for VS 2005 and 2008.</p> <p>You will need to use MSBEE <a href="http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSBee" rel="nofollow noreferrer">http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSBee</a></p> <p><a href="http://devlicio.us/blogs/ziemowit_skowronski/archive/2008/08/22/working-with-net-1-1-in-visual-studio-2008-and-team-server.aspx" rel="nofollow noreferrer">Working with .NET 1.1 with Visual Studio 2008</a></p> <h3>Some tips</h3> <p>Open up *.csproj and find out where the SharePoint dll is referenced and change to something like this which changes the referenced assembly depending upon your target (FX1_1 means you are targeting .NET1.1 and therefore WSSv2)</p> <pre><code>&lt;Reference Include="Microsoft.SharePoint"&gt; &lt;HintPath Condition="'$(TargetFX1_1)'!='true'"&gt;pathto\WSS3\Microsoft.SharePoint.dll&lt;/HintPath&gt; &lt;HintPath Condition="'$(TargetFX1_1)'=='true'"&gt;pathto\WSS2\Microsoft.SharePoint.dll&lt;/HintPath&gt; &lt;/Reference&gt; </code></pre> <p>Use conditional compilation for differences where necessary</p> <pre><code>#if FX1_1 // WSSv2 specific code #else // WSSv3 specific code #endif </code></pre> <p>If you get a compiler error but the code looks right it may be that the error is only for .NET1.1 / WSSv2 and compiles fine in .NET2/WSSv3. Check the output tab to see for which target the error occurred</p> <p>You will also need to master some MSBUILD ninja moves to keep a 1 step build process and keep yourself sane <a href="http://brennan.offwhite.net/blog/2006/11/30/7-steps-to-msbuild/" rel="nofollow noreferrer">http://brennan.offwhite.net/blog/2006/11/30/7-steps-to-msbuild/</a> using MSBUILD you can get VS to compile both versions at the same time without resorting to the command line.</p> <p>This will run the .NET1.1 compilation after .NET has finished and output some messages to the Output window to help you work out where errors occurred.</p> <pre><code>&lt;Target Name="BeforeBuild"&gt; &lt;Message Text="--- Building for .NET 1.1 ---" Importance="high" Condition="'$(TargetFX1_1)'=='true'" /&gt; &lt;Message Text="--- Building for .NET 2.0 ---" Importance="high" Condition="'$(TargetFX1_1)'!='true'" /&gt; &lt;/Target&gt; &lt;Target Name="AfterBuild" Condition="'$(TargetFX1_1)'!='true'"&gt; &lt;MSBuild Projects="$(MSBuildProjectFile)" Properties="TargetFX1_1=true;" /&gt; &lt;/Target&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to reference two versions of an API?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRyan
    1. USRyan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to reference two versions of an API?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload