About Windows Installer, the .NET Framework, and Visual Studio.
Setup and deployment is a tricky business. Machines can be in many different and often unforeseen states that cause setup to fail. But rarely will setup actually crash, and that is why setup logs are vital to diagnose install, repair, and uninstall problems.
Setup applications for Visual Studio and .NET may write to many different logs because the products are actually comprised of many different packages. Aaron Stebner had documented several log file names for Visual Studio 2008, but with our new and improved patch wrapper we may write even more log files. As we onboard new CTPs for great new features in Visual Studio the list of log files may also grow.
So our QA team has written a tool to collect all these logs for VS 2005 and 2008, and .NET 2.0 through 3.5 aptly named, collect.exe. The link below is an updated version of the old collect.exe that you should use when reporting bugs with setup.
If you encounter any setup issues, we will need all relevant logs. Please follow the instructions below to collect all those logs.
There are several options for reporting setup errors, but you might consider first checking to see if the issue is a known issue. This will save you time and provide more immediate results. In most scenarios, there will be a link on the error page after setup completes. Clicking on this should provide a smaller log that highlights the errors encountered. To dig deeper, check out some of the tips provided on Aaron's blog and on my blog.
If you would like to report an error, be sure to collect logs as described above and choose from the options below.
Summary Microsoft Silverlight Tools Beta 1 for Visual Studio 2008 is not compatible with Visual Studio
Visual Studio SP1 beta is available for Download, it includes hundreds of bug fixes and customer-reported
Ieri dimineata a fost facut public VS 2008 SP1 Beta 1. Mai multe informatii despre ce contine SP1 se
Sorry for being a bit late to the game...  I should have posted yesterday but I've been drowning. 
One of many improvements made to Visual Studio 2008 Service Pack 1 is that VS 2008 SP1 Beta customers
That tool is difficult to use under Vista as common user. The output directory blinks on the screen for 1 second and it goes away. The output is not saved under %temp% but under the admin sccount.
Arne, because our setup requires admin privileges the collection log must collect those logs (for the admin user); so, credentials (or acceptance of the UAC if you're already an admin) are required to collect admin logs and the CAB is placed in %TEMP% - which is now the admin's %TEMP% (as designed).
少し���れてしまい申し訳ありません。昨日のうちに投稿するはずだったのですが、ゲームにはまってしまいまして...。既にご存知かと思いますが、2008 SP1 Beta をリリースしました。ぜひお試しいただき、フィードバックをお寄せくださいますようよろしくお願いいたします。TFS
Visual Studio （以下 VS ） 製品のインストールで生成されるセットアップログファイルを収集するツールを紹介したいと思います。 VS 製品のセットアップは .NET Framework ランタイムを始め複数のコンポーネントをインストールするため、
I have a error on the instalation of the SP 1 of VS 2008.net, I have installed silverligth 2.0 and eht official web of microsoft says not has conflict between SP1 of VS2008 and silverligth 2, but I do not install the two programs to this time.
If any body knows the order of installation of
this tools help me please
PD.
Sorry by my poor English
Oscar76, Brad's blog at http://weblogs.asp.net/bradleyb/default.aspx has a lot of information about installing Silverlight and how to work around issues.
Following on the release last week of SQLServer 2008 , we are proud to announce the release of Visual
Service Packs for VSTS/TFS do not only contain bug fixes, but quite a few nice new features as you can
再びこんにちは！ 今日は僕の頭の中で動いている CPU の調子がすこぶる快調なので、英語スレッドの日本語版をもう 1 つ紹介してみようと思います。 これは、米国マイクロソフト社に勤務する Heath Stewart
hi..
Actually i wanted to connect MS Acess 2007 using C# and so i wrote this code for it..
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace Win8
{
public partial class Form1 : Form
public Form1()
InitializeComponent();
}
OleDbConnection con = new OleDbConnection();
private void Form1_Load(object sender, EventArgs e)
con.ConnectionString = "provider=microsoft.Jet.OLEDB.4.0;Data Source=..\\Rhi1.mdb";
con.Open();
label1.Text = "Connected";
con.Close();
And aftr doing it so i am getting the error as "microsoft.jet.oledb.4.0 provider is not registered" I searched the solution on net and got this as how to resolve it..
1. From the solution explorer right-click your project then click Properties
2. Click the Build tab
3. Change Platform target from: Any CPU to x86
4. Re-build your solution
After doing it so the output is coming as just the form with "label1" on it
instead of showing the word "Connected" in the form..
so do i need to use VmWare Workstation nd put a Windows Xp Cd to make the code work ..
pls help..