Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | More fixes to wording on the download page. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | preRelease |
| Files: | files | file ages | folders |
| SHA1: |
0222f3b0da0048eca24404218bebf717 |
| User & Date: | mistachkin 2013-12-23 17:11:25 |
Context
|
2013-12-23
| ||
| 21:40 | Make sure the Visual Studio auto-detection batch file actually marks Visual Studio 2013 as 'found' when necessary. check-in: d1e12db1d9 user: mistachkin tags: preRelease | |
| 17:11 | More fixes to wording on the download page. check-in: 0222f3b0da user: mistachkin tags: preRelease | |
| 16:50 | Another minor download page update for Visual Studio 2013. check-in: c0e81f8271 user: mistachkin tags: preRelease | |
Changes
Changes to www/downloads.wiki.
196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 |
runtime. Typically, these packages are used in cases where customer
machines may not have the necessary version of the Visual C++ runtime
installed and it cannot be installed due to limited privileges.
<br /><br />
The next step is to identify the version of the
<a href="http://en.wikipedia.org/wiki/.NET_Framework">.NET Framework</a>
being targeted by the application.
In theory, assembly binaries for the
<a href="http://go.microsoft.com/fwlink/?LinkID=32168">.NET Framework
2.0</a> will work with the
<a href="http://go.microsoft.com/fwlink/?LinkID=186913">.NET Framework
4.0</a>; however, this is not ideal. Furthermore, assemblies compiled
for the .NET Framework 4.0 cannot be loaded by the .NET Framework 2.0.
</td>
</tr>
<tr>
<td colspan="3" class="importantHeader">
<b>Using Native Library Pre-Loading</b>
</td>
|
| > > | < < > > > > |
196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 |
runtime. Typically, these packages are used in cases where customer
machines may not have the necessary version of the Visual C++ runtime
installed and it cannot be installed due to limited privileges.
<br /><br />
The next step is to identify the version of the
<a href="http://en.wikipedia.org/wiki/.NET_Framework">.NET Framework</a>
being targeted by the application.
Generally, assembly binaries linked against the
<a href="http://go.microsoft.com/fwlink/?LinkID=32168">.NET Framework
2.0</a> (or the
<a href="http://go.microsoft.com/fwlink/?LinkId=124150">.NET Framework
3.5</a>) will work with the
<a href="http://go.microsoft.com/fwlink/?LinkID=186913">.NET Framework
4.0</a> (or higher); however, this is less than ideal. Furthermore,
assemblies linked against the .NET Framework 4.0 (or higher)
<b>cannot</b> be loaded by any versions of the .NET Framework prior to
4.0.
</td>
</tr>
<tr>
<td colspan="3" class="importantHeader">
<b>Using Native Library Pre-Loading</b>
</td>
|