Service Pack 1 for VS 2008 and .NET FX 3.5 released!
We released Visual Studio 2008 and the .NET Framework 3.5 last November. The feedback has been tremendously positive, but developers always have new ideas and suggestions for how we can improve the development experience for them.
Building on the base of great features in VS2008 and .NET 3.5, I am happy to announce today the release to manufacturing of the .NET Framework 3.5 SP1 and Visual Studio 2008 SP1.
In Visual Studio 2008 SP1 we have concentrated on improving performance and reliability. We have worked on our designers for building WPF applications and improved their performance, we have improved tools for developing AJAX applications, improved designers for working with the ADO.NET Entity Framework, and included a richer JavaScript development environment and a streamlined Web site deployment experience.
In the .NET Framework we went a little further. Beyond fixing the customer reported bugs we also added some highly requested features to make it easier to develop applications for the latest platforms. Some of these new features include the .NET Framework Client Profile, enhanced support for database application development through the ADO.NET Entity Framework, ADO.NET Data Services and integration with (recently released!) SQL Server 2008, and multiple enhancements to ASP.NET.
Whenever we talk to developers, one of the major pain points that they face is deployment of their .NET applications due to the time it takes to install the .NET Framework. This is something we know we needed to work on and have delivered a great solution in SP1 with the .NET Framework Client Profile.
The .NET Framework Client Profile setup contains just those assemblies and files in the .NET Framework that are typically used for client application scenarios. This reduced size framework (86.5% reduction from 197MB to 26.5MB) is the fastest and easiest way to deploy Windows applications. The .NET Framework Client Profile also makes it possible to extend the improved download and installation experience to existing .NET applications. As an added bonus, with work done in the service pack, services connecting to .NET applications will also see up to 10 times the amount of performance improvement when running in Internet Information Services (IIS) 7.0.
Continuing to focus on the development of Web 2.0 applications and dynamic Web sites, ASP.NET Dynamic Data is now offered with SP1 which provides a rich scaffolding framework that allows rapid data-driven development without writing code.
This release also comes right in step with the recent release of SQL Server 2008. With this service pack, Visual Studio 2008 and the .NET Framework 3.5 also support SQL Server 2008, making the Microsoft platform the most comprehensive environment for database application development. The .NET Framework 3.5 SP1 includes ADO.NET Data Services and ADO.NET Entity Framework, which raise the level of abstraction for database programming and supply both a new model-based paradigm and a rich, standards-based framework for creating data-oriented Web services.
This release of SQL Server is very important to us for the developer community and it is special in another way for me personally. This week marks the ten year anniversary of the India Development Center which I started and continue to sponsor. SQL Server 2008 is the first SQL release with significant in-box contributions from this development center including SQL Server Compact 3.5.1. I am very proud of the work that they have done on this release.
Namaste!
Comments
Anonymous
August 11, 2008
PingBack from http://www.easycoded.com/service-pack-1-for-vs-2008-and-net-fx-35-releasedAnonymous
August 11, 2008
Al día de hoy se ha liberado el service pack 1 de VS2008 y el NET Framework 3.5 . Este Service Pack contieneAnonymous
August 11, 2008
Today we shipped Service Pack 1 (SP1) for both Visual Studio 2008 and the .Net Framework 3.5.  ThisAnonymous
August 11, 2008
Microsoft .NET Framework 3.5 Service Pack 1, Visual Studio 2008 Service Pack 1, and Team Foundation ServerAnonymous
August 11, 2008
Pingback from: http://blogs.telerik.com/KevinBabcock/Posts/08-08-11/visual_studio_2008_service_pack_1_rtm_is_live_.aspxAnonymous
August 11, 2008
Publicación del inglés original : Lunes, 8 de agosto de 2008 10:12 AM PST por Somasegar . El pasado mesAnonymous
August 11, 2008
Soma, senior VP of the Developer Division, just announced on his blog that the Service Pack 1 for VSAnonymous
August 11, 2008
My congratulations to the entire MS DevDiv, and to the Visual Studio team in particular. This was a long-awaited release with lots of tasty new stuff, and it's great to finally get all the goodness (also, at least one of my Connect feature requests is implemented in there, and that just feels good). Though why shyly call it a "service pack", when it's really and obviously much more than that, is beyond me... Oh yes, and bring it on! We're already waiting for Entity Framework 2 with full roundtrip here :)Anonymous
August 11, 2008
Just in case mine is the only blog you subscribe to, SP for the MS developer platform is out now.  Anonymous
August 11, 2008
El dia de hoy fue lanzado el SP1 de Visual Studio 2008 y .NET Framework 3.5 . Aquí les comparto un mensajeAnonymous
August 11, 2008
This morning, we’ve shipped Visual Studio 2008 SP1 & .NET 3.5 SP1 to the web. Soma has moreAnonymous
August 11, 2008
Visual Studio 2008 and .NET Framework 3.5 Service Pack 1 ReleasedAnonymous
August 11, 2008
The comment has been removedAnonymous
August 11, 2008
Vincent - If you have setup issues, a great first resource is Heath's blog: http://blogs.msdn.com/heaths/archive/tags/VS+2008+SP1/default.aspx. Here's a useful entry about collecting setup log information and where to get help: http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx -MeghanAnonymous
August 11, 2008
Great!! I thought VS2008 SP1 was expected towards the end of the year with Silverlight 2. So is Silverlight 2 RTM pretty close to RTM as well; like is it also expected this month? What about Blend 2.5?Anonymous
August 11, 2008
Service Pack 1 for Visual Studio 2008 and .NET Framework 3.5 is out now. We had a chance to work MicrosoftAnonymous
August 11, 2008
Very Quick Note: Visual Studio 2008 Service Pack 1 was released finally (in combination with .NET FrameworkAnonymous
August 11, 2008
Visual Studio 2008 Service Pack 1 has been released and it's available on the Microsoft Download Center.Anonymous
August 11, 2008
"Basados en las mejores características de VS2008 y .NET 3.5, estoy satisfecho de anunciar hoy el lanzamiento...Anonymous
August 11, 2008
As noted earlier today in this post on Soma's blog , the .NET Framework 3.5 SP1 and Visual Studio 2008Anonymous
August 11, 2008
Please do not install this SP1 if you are doing Silverlight development using Entity Framework or WCF/ADO Dataservices as Silverlight 2b2 is incompatible with this Service Pack. These will not work and you will be forced back to SP1 Beta 1. ThanksAnonymous
August 11, 2008
ping back from [bits.samiq.net] [... check out the official post on the release at Soma's Blog ...]Anonymous
August 11, 2008
Somasegar's WebLog : Service Pack 1 for VS 2008 and .NET FX 3.5 released! (소식) Download details VisualAnonymous
August 11, 2008
Congrats, Soma! I just finished my install and it all went smoothly. I can't wait to explore it. -TylerAnonymous
August 11, 2008
E gata și SP1 , cu suport complet pentru SQL Server 2008 (inclusiv VSTS), cu WPF și WCF optimizate, cuAnonymous
August 11, 2008
Visual Studio 2008 and the .NET Framework 3.5 Service Pack 1 (SP1) is not a traditional service packAnonymous
August 11, 2008
That's right, SP1 for Visual Studio 2008 and .NET Framework 3.5 went live today . You can read aboutAnonymous
August 11, 2008
Microsoft has now released the final bits of Visual Studio 2008 Service Pack 1 and the .NET Framework 3.5 Service Pack 1, download here. A lot of stuff has been improved such as stability and performa...Anonymous
August 11, 2008
出ましたねー。 今回のは単なるバグフィックス集ではなく、けっこう新しい機能等が入っているので、期待...Anonymous
August 11, 2008
No proszę, cały czas przedzieram się przez pourlopową skrzynkę i dociera do mnie coraz większy updateAnonymous
August 11, 2008
As mentioned yesterday .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 were released. Here is a moreAnonymous
August 11, 2008
My WoRm Congratulations to all the teams in the Dev. division and especially to Soma and ScottGu I am veryexcited about all of these releases... MohamedAnonymous
August 12, 2008
This would have been great news... but it seems that the .NET 3.5 SP1 breaks the use of WPF under IIS. (Why would anyone do that? Well it's a really nice way of building up images on-the-fly, ready for serving out for use in a web application). There's a thread up at forums.asp.net: http://forums.asp.net/t/1299963.aspx Is there anyone we could contact at MS to look into this issue? Thanks in advance, Stu Smith (stusmith at pobox dot com)Anonymous
August 12, 2008
As you probably know by now, we've released Visual Studio 2008 Service Pack 1 and the .NET FrameworkAnonymous
August 12, 2008
Compilation for web sites under 3.5 raises an error see: http://forums.asp.net/t/1304386.aspx for the problem and my work-around Also, NTML auth breaks for the debugger under Win 2003, IIS6 and VS 2008 SP1. I simply cannot debug any sites with sp1. I hate to say it, but for the first time ever I am recommending that no-one installs this SP. Regards Jim Losi C# MVP 2007-2008Anonymous
August 12, 2008
In case you haven't heard, the .Net FX 3.5 Service Pack 1 and VS 2008 Service Pack 1 have been released!Anonymous
August 12, 2008
The comment has been removedAnonymous
August 12, 2008
The comment has been removedAnonymous
August 12, 2008
The comment has been removedAnonymous
August 12, 2008
Hello Jim, Thank you for reporting the issue about NTLM auth not working for debugging with SP1 on Win2k3 for IIS6. With your help we were able to narrow down the issue to a change which affects debugging on Win2k3 when using custom host headers in IIS. The version of system.dll in SP1 contains a include a loopback check security feature that is designed to help prevent reflection attacks on your computer. This same check also prevents debugging with custom host headers on Win2k3. Fortunately a simple workaround exists to the the issue that enables debugging for this particular scenario. The workaround is described in this KB article: http://support.microsoft.com/kb/896861 Thanks again for your help in identifying the issue and bringing it to our attention. Omar Khan | Visual Studio Product TeamAnonymous
August 12, 2008
Will there be a separate SP2 release for just .NET 2.0 like there was .NET 2.0 SP1 which can be installed on Windows 2000 SP4?Anonymous
August 12, 2008
One of the nice feature I saw in "Visual Studio 2008 Team Foundation Server Service Pack 1" is "Links to Team System Web Access pages from notifications". Unfortunately i found no documentation how to enable it. After deep searching in the files of the SP1 update package found and option for TfsAdminUtil.exe that will enable this functionality. (TfsAdminUtil.exe configureconnections /TSWAUri:<uri>) I was happy that i found it until I saw the result of it. The sourcecontrol checkin notification doesn't works well. For more details see my feedback to Microsoft: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=361594 It's possible that I'm missing something so I'm waiting for others to try it also. Regards, David.Anonymous
August 13, 2008
You're welcome, Omar. Happy to help :)Anonymous
August 13, 2008
Would love to install it, but the installation failed : ps: Maybe I have to remove silverlight 2beta first <g>Anonymous
August 13, 2008
We just announced the release of Service Pack 1 for VS 2008 and .NET FX 3.5 . A major push for this releaseAnonymous
August 13, 2008
We just announced the release of Service Pack 1 for VS 2008 and .NET FX 3.5 . A major push for this releaseAnonymous
August 13, 2008
[Updated 8/13/2008 with the release of Visual Studio 2008 SP1.] With the many releases of the MicrosoftAnonymous
August 13, 2008
See Soma's blog entry for more information.  Also, I updated the table that maps Visual Studio versions,Anonymous
August 13, 2008
SP1 is here ; complete with the revved 3.5 Enhancements Training Kit. Jonathan reveals all , includingAnonymous
August 13, 2008
David, I've posted in your MSDN forum thread the details on the issue with checkin notification emails. http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3744309&SiteID=1&mode=1 BuckAnonymous
August 13, 2008
Echo Chamber ; SP1 for VS 2008 and .NET 3.5 released;Anonymous
August 13, 2008
Soma announced the availability of Visual Studio 2008 Service Pack 1 and .NET 3.5 Service Pack 1 . InstallationAnonymous
August 14, 2008
My experience just seems to be echoing a previous comment. Silverlight2 Beta2 does not seem to work with the RTM version of VS 2008 SP1. It may be some kind of corruption in the new version of Silverlight2 Beta2 that is preventing it from installing. It may be something that I am not understanding about the sequence of installs that is supposed to get this to work. But I don't need Silverlight. Now that I have totally removed Silverlight2 from my system I don't seem to be having any problems with VS2008 SP1 or .net 3.5 SP1. I will not try to install Silverlight again until there is good reason to expect it to work.Anonymous
August 14, 2008
Please do not release anything without testing all your development products together. VS.NET, Service Packs, etc must work with SQL Server 2008, Silverlight, and any other development/design products (like Expression Studio 2). Why does Microsoft expect users of its products to suffer un-install, re-install and other non-sense to get these common development products to work together in harmony everytime a new SP is released. I must add that removing beta products is sometimes a nightmare situation. The transition from installed beta products to installing RTM products needs improvement.Anonymous
August 14, 2008
Ack! Installed Visual Studio Tuesday. Succeeded but poorly, many problems, including several odd errors and warnings in application and system logs. After a full day Wednesday of removing everything Visual Studio and .NET related (hard, they broke, wouldn't repair, wouldn't uninstall, wouldn't force reinstall) and tweaking services I finally managed to get .NET versions back and only have no errors or warnings in logs. This morn I started by installing Visual Studio, partial install. Succeeded with ony two odd errors in logs. Whoa, what's this now, Service Pack 1 for VS 2008 and .NET FX 3.5. Ok, let's get it over with. First thing I noticed one hour into the install was that the service pack was installing things I chose not to install. The trouble started when I rebooted though. The install somehow trashed my administrator account. Rolled back via system restore. Ack! Everything Visual Studio and .NET is still wacky. Can't repair, must roll back further and reinstall all. Long day ahead of me - again.Anonymous
August 14, 2008
The comment has been removedAnonymous
August 14, 2008
Jim, (Jim Losi): We apologize for the inconvenience the ASP.NET compilation issue you reported has caused and really appreciate all the help you have been giving us to resolve the issue. The behavior you are seeing is the original behavior of ASP.NET 2.0. When the .NET Framework 3.5 and Visual Studio 2008 were introduced, a bug was introduced that affected certain pageBaseType scenarios that unfortunately were not intended. It seems as if you might have run into one of these scenarios. In the .NET Framework 3.5 SP1, the bug was fixed and these scenarios no longer occur; pageBaseType again works the same as in ASP.NET 2.0, as requested by customers. Unfortunately, this means that customers who have relied on the unintended behavior that was introduced in the .NET Framework 3.5 will now encounter problems when they run their applications. We are now evaluating creating a HotFix for these scenarios and providing workarounds for customers to help with this issue. Here are some details about the issue; we will post a more detailed description soon. The mismatch is caused by the class in the code file not being assignable to the pageBaseType that is defined in the web.config file. The sequence that occurs is this:
- During code generation for a page (MyPage.aspx) in a Web site, ASP.NET creates a separate class from the class that is defined in the code-behind file source (MyPage.aspx.cs). The web.config file’s pageBaseType value can be used in cases where you want all pages to have certain properties. It applies to all pages, not just to pages that do not have code-behind files.
- If MyPage.aspx has a CodeFile attribute and therefore inherits from a class that is defined in MyPage.aspx.cs, the class defined in MyPage.aspx.cs must extend the pageBaseType class. To work around this problem, you can do the following:
- If the pageBaseType class (for example, MyBasePage) is not needed for all pages, you can remove it from the web.config file, or;
- Where pages do require the pageBaseType value, modify the classes in the code-behind files to extend the base type. In the filename.aspx.cs code-behind file, make sure that the class inherits from the pageBaseType that is specified in the web.config file (for example, public partial class CodeFileClass : MyBasePage instead of public partial class CodeFileClass : System.Web.UI.Page).
- An alternative workaround will allow you to add the following attribute to your page directive: CodeFileBaseClass="System.Web.UI.Page" Again, thank you for your help in resolving the problem.
Anonymous
August 15, 2008
I agree with several above posters that the deployment situation is real bad for the .NET Framework even if MS has introduced the client profile.Anonymous
August 15, 2008
The comment has been removedAnonymous
August 15, 2008
Download link of MSDN Library for Visual Studio 2008 SP1, referenced in "Visual Studio 2008 Service Pack 1 (SP1) Readme", is BROKEN the link is: http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/www.microsoft.com/downloadsAnonymous
August 15, 2008
The comment has been removedAnonymous
August 15, 2008
Sorry, i forgot to tell that our server runs the Windows Server 2008 Enterprise Edition in Portuguese language with all the security updates and no third part software installed... The only thing we installed is the IIS 7 and nothing else. But even so the server does not accept the installation of ASP.Net 3.5 SP1. We already tried to install the ASP.Net 3.5. After that, we tried to install ASP.Net 3.5 SP1 and even so the installation hangs out at the same point and the error log shows the same message above.Anonymous
August 15, 2008
Why is the .NET Client Profile (255 MB) larger than the .NET Framework full package (231 MB)? I thought, the Client Profile was to ease the deployment scenarios?Anonymous
August 16, 2008
The comment has been removedAnonymous
August 16, 2008
But there is no solution for non-internet based deployments. This is where MS is missing the point. What's the problem in making x86, x86-64 and IA-64 separate?Anonymous
August 16, 2008
Visual Studio 2008 Service Pack 1 and .NET Framework 3.5 Service Pack 1 is out the door. See http://msdn.microsoft.com/en-us/vstudio/products/cc533447.aspxAnonymous
August 17, 2008
原文地址 ： Service Pack 1 for VS 2008 and .NET FX 3.5 released! 原文发表时间 ： Monday, August 11, 2008 10:12 AMAnonymous
August 17, 2008
I request Microsoft to make available a separate .NET 2.0 SP2 for those who want have Windows 2000 and those who can't/don't want to install .NET 3.5 SP1 yet.Anonymous
August 17, 2008
Congratulations Soma and all the Microsoft team. The SP1 just finished installing, and went smooth. As a student, I am really looking forward to experiencing the new improvements. Cheers.Anonymous
August 18, 2008
The comment has been removedAnonymous
August 19, 2008
Sorry, i forgot to tell that our server runs the Windows Server 2008 Enterprise Edition in Portuguese language with all the security updates and no third part software installed... The only thing we installed is the IIS 7 and nothing else. But even so the server does not accept the installation of ASP.Net 3.5 SP1. We already tried to install the ASP.Net 3.5. After that, we tried to install ASP.Net 3.5 SP1 and even so the installation hangs out at the same point and the error log shows the same message above.Anonymous
August 19, 2008
Please make just the client profile (offline version) available for download instead of bundling the full .NET along with it. Kind of defeats the purpose. Also, the deployment guide states that the XPS Essentials Pack isn't included in the client profile. However the downloadable XPS Essentials Pack right now isn't installable on XP SP3 and gives an error message.Anonymous
August 19, 2008
The comment has been removedAnonymous
August 20, 2008
The comment has been removedAnonymous
August 20, 2008
has released . w00t! For the XML Tools team this is an especially big release since SP1 is the vehicleAnonymous
August 25, 2008
Earlier this month, we released .NET 3.5 SP 1 .  One of the new features available in this updateAnonymous
August 26, 2008
Is the .NET Framework 3.5 sp1 available as an iso too?Anonymous
August 26, 2008
The comment has been removedAnonymous
August 27, 2008
The comment has been removedAnonymous
August 28, 2008
I have a question about VS 2008 SP1 and publishing an ASP.NET web site. It used to allow you the option of having a merged single assembly, why has it been taken out? I know you can do it through a web deployment project but how is this making any ones life easier? Is there some best practice being forced here? thanks ChadAnonymous
August 29, 2008
Hi Chad, AFAIK Publish Web did not allow merging of assemblies at all... In Publish Web we just call aspnet_compiler.exe which does the pre-compilation... It was always WDP which use to do the merging by calling aspnet_merge.exe... I am very curious to understand the potential impact and the features that you are seeing missing, could you send me an email at Vishal.Joshi@Microsoft.com to discuss this further... Thanks VishalAnonymous
September 16, 2008
Somasegar, Is there any information on compatibility with 3.5 sp1 code deployed onto non-sp1 machines? Specifically, what it will break? I support apps for multiple clients and not all of them have upgraded to sp1 on their servers yet. I want to upgrade to my local workstation & visual studio to sp1, but I don't know how to support multiple sp1 targets. Thanks, --jbAnonymous
September 18, 2008
The comment has been removedAnonymous
September 26, 2008
You guys really ought to fix text rendering, datagridview, data binding and sluggish performance of GDI+ in general for WinForms. Why has this been ignored for so long? Why not accelerate it properly once and for all with those monster GPUs? Why is the footpring of WPF and Silverlight so huge that even pathetically slow WinForm outperforms it by a factor of 5? Why not fix the problems and actually invest in the tech you gave us before pushing another, even more bloated one? The benefits are so huge I cannot believe your strategy at all. Most drop-outs from evaluating all your new tech are related to performance and poor rendering against real-world, heavy-stress, heavy-updating scenarios for the UI. WPF and Silverlight make it much worse, despite being a great tech, they are unusable for snappy apps users, put simply, demand.Anonymous
September 26, 2008
Raspen, we always take performance very seriously and while there are inherent limits to how much we can improve GDI+ we'll look in to what more can be done. I'm not exactly sure what you mean by “footprint” but WPF is significantly smaller and faster with SP1 and the Client Profile (thanks to increased hardware acceleration). Silverlight RC1 also has significant performance improvements that should be noticeable. If you wouldn’t mind sending me your scenarios in more detail I’ll look in to what the issues might be in more detail. Thanks, Ian.ellison-taylor@microsoft.comAnonymous
November 05, 2008
Dear sir, if I reinstall windows xp and I want to use vs2008, I should install .net framework 3.5 sp1 onlyor install 3.5 then 3.5 sp1. thanks for you answer.Anonymous
November 05, 2008
Hi Mizma2K, If you install VS 2008 after you re-install Windows XP, you install .NET FX 3.5 as part of the VS install. In that case, you need to install .NET FX 3.5 SP1 to get the latest framework bits. -somasegarAnonymous
November 13, 2008
I can't install this service pack and it has been killing my brain this for a week. The installer stops downloading and progressing and becomes unresponsive without any logs,errors or whatsoever. Please help :(Anonymous
November 13, 2008
[Responding to George's post on Nov. 13] George, can you please provide contact information so we can connect directly? I'd like to help.Anonymous
November 24, 2008
I can't install the service pack because the Removal tools of visual studio 2008 ask for a visual studio Media. I can't continue and the tool rollback the installation. I'm very confused...Anonymous
November 24, 2008
Hi Jordi. Can you provide contact information so we can follow up directly. Thanks!Anonymous
February 06, 2009
The comment has been removedAnonymous
May 06, 2009
Hi soma!!! In VS 08 SP1 a new frmwork called "Client Profile frmwork 3.5 sp1" has been provided. can you help me how to provide this frmwork with deployment project(offline installation) or installables??Anonymous
May 07, 2009
Hi Abhjit, There's one important caveat associated with offline installations of the .NET Framework 3.5 SP1 Client Profile. If the target machine does not support the Client Profile, either because it's not an XP machine or because the machine already has a previous version of the Framework installed, the full .NET Framework 3.5 SP1 installer will be downloaded and executed instead. This means for offline scenarios you'll potentially only gain on installation speed. If that suffices for you as a motivator, continue reading. If not, it might be easier just to roll out the full .NET Framework 3.5 SP1 installer as part of your package. The main scenario for Client Profile is fast web installs where we download while installing, etc. Now to the real stuff. Considering the primary goal of using the Client Profile for web deployment scenarios, Visual Studio 2008 SP1 comes with the "product definition" for an online Client Profile installation. See %ProgramFiles%microsoft sdksWindowsv6.0ABootstrapperPackagesDotNetFx35Client for this definition, which is where the Prerequisites dialog in Visual Studio 2008 SP1 gets its data from. All this product.xml file tells the bootstrapper is how the executable installer for the Client Profile is called (i.e. DotNetFx35ClientSetup.exe). During build time of your Setup and Deployment Project, that binary gets included in the offline package and copied from the aforementioned location. You can find this online package at http://www.microsoft.com/downloads/details.aspx?FamilyID=8cea6cd1-15bc-4664-b27d-8ceba808b28b&DisplayLang=en This explains how the online scenario is intended to work. However, as you want to go for an offline installation, you should grab the offline installer from http://www.microsoft.com/downloads/details.aspx?FamilyID=992cffcb-f8ce-41d9-8bd6-31f3e216285c&DisplayLang=en and place it in that folder. You'll have to rename it from DotNetFx35Client.exe to DotNetFx35ClientSetup.exe for Visual Studio to pick it up based on the product.xml file that points to it. Notice the file size of the offline package. This is the combined size of the installers for both the Client Profile, around 25 MB, and the full framework, around 230 MB. To be truly offline and for reasons explained at the beginning of this comment post, we have to include both in the offline package. Keep in mind this is merely a work-around as the Client Profile was primarily designed and tested for online scenarios. If you have further questions, feel free to contact me directly at bartde at microsoft dot com. Hope this helps, -BartAnonymous
August 17, 2009
Is there some best practice being forced here? thanksAnonymous
July 01, 2011
THXXXXXXXXXXXX