Me, Myself and Mayvelous

Archive for the ‘VS.Net’ Category

I was trying to deploy a .NET 2.0 application using ClickOnce Deployment the other day.
I had all the IIS settings configured and folder paths entered correctly.
When I clicked ‘Publish Now’, I got an error message that made me wonder if I needed to reinstall Visual Studio.

Cannot publish because a project failed to build.
Could not find required file ‘setup.bin’ in ‘C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Engine’.

Publishing ClickOnce Deployment

My first reaction was oh damn, I don’t want to reinstall whatever it is that’s broken.
My second smarter reaction was to google the error :)
Found this post on MSDN forums.

Basically, it was AVG Antivirus 8.0 that incorrectly identified and quarantined a required file as a Trojan.
AVG Free marked the file C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Engine\setup.bin as a Trojan horse BackDoor.VB.DIY

AVG Free Virus Vault

Simply select the file and click the ‘Restore’ button from AVG’s Virus Vault. (So glad I havn’t been emptying my vault!)

Once that little error was corrected, it was a simple matter to click ‘Publish Now’ again and I was happily on my way to my first ever ClickOnce Deployment!
I’m glad it wasn’t a serious problem requiring reinstalls.

Some days, I wonder if I want to keep an antivirus program running on my computer.
I don’t need much protection as I am careful in my mail box and I rarely visit websites out of google’s domain.
Google Reader gets me everything I want to read anyway.
Scratch that thought I lend my flash drive out to other people sometimes so it wouldn’t be a good idea to have no protection.
I trust myself but you just can’t trust people’s machines.

Just going through my feeds and this one interests me. There is an announcement of the next version of Visual Studio and .Net Framework: Visual Studio 2010 and .Net Framework 4.0.

Visual Studio 2010 and the .NET Framework 4.0 mark the next generation of developer tools from Microsoft. Designed to address the latest needs of developers, Visual Studio and the .NET Framework deliver key innovations in the following pillars:

  • Democratizing Application Lifecycle Management
    Application Lifecycle Management (ALM) crosses many roles within an organization and traditionally not every one of the roles has been an equal player in the process. Visual Studio Team System 2010 continues to build the platform for functional equality and shared commitment across an organization’s ALM process.
  • Enabling emerging trends
    Every year the industry develops new technologies and new trends. With Visual Studio 2010, Microsoft delivers tooling and framework support for the latest innovations in application architecture, development and deployment.
  • Inspiring developer delight
    Ever since the first release of Visual Studio, Microsoft has set the bar for developer productivity and flexibility. Visual Studio 2010 continues to deliver on the core developer experience by significantly improving upon it for roles involved with the software development process.
  • Riding the next generation platform wave
    Microsoft continues to invest in the market leading operating system, productivity application and server platforms to deliver increased customer value in these offerings. With Visual Studio 2010 customers will have the tooling support needed to create amazing solutions around these technologies.
  • Breakthrough Departmental Applications
    Customers continue to build applications that span from department to the enterprise. Visual Studio 2010 will ensure development is supported across this wide spectrum of applications.

Here is a full overview of Visual Studio 2010 and .NET Framework 4.0 and some more reading on vSTS 2010 (code-name “Rosario”): What’s new in Visual Studio Team System 2010. Read some more detail announcement on Somasegar’s (senior vice president of the Developer Division at Microsoft) post: What’s next for Visual Studio and .NET FX?

Ok, that’s about it for now.

Just an aside note for myself.

Visual Studio Gallery
A place where all developers can go to find extensions to Visual Studio. The site has everything from community built power toys for VS to industry partner solutions for enterprise development.

MSDN Code Gallery
MSDN Code Gallery is your destination for downloading sample applications and code snippets , as well as sharing your own resources.

Via: (#) | (#)

Updated: New Features. Thx Anthony.

This was a humongous pain for me and took quite a lot of my time so just noting down a few points for self reference. Previously, I have Visual Studio 2005 and SQL Server 2005 installed on my Vista machine and they worked just fine. Now we are upgrading to VS2008, I uninstalled everything related to VS2005 then reinstall SQL Server 2005 and things got screwed up. Check out the failure list that I got – pretty much everything failed.

MS SQL Server 2005 Setup Errors

The worst thing about this installation is that, it takes ages to install till the end, then shows up the error message box.

Program Versions:

# SQL Server 2005 – Developer Edition
# Windows Vista Ultimate
# Visual Studio Team Suite 2008

Make sure you cross check Hardware and Software Requirements for Installing SQL Server 2005 before installation.

The first error/warning I tried to fixed was about IIS requirement. I’m sure I have IIS7 enabled on my Vista and also enabled IIS6 compatiblity mode but that is not enough and have to enable some more features.

System Configuration Check

System Configuration Check: IIS Feature Requirement
Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove programs in Control Panel or enable the IIS server through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.

I think it is to do with Installing SQL Server 2005 Reporting Service on Vista, untill or unless you enable all those features the Reporting services cannot be installed.

The main features to turn on are as mentioned here but I turned on almost everything just to make sure.

IIS 7 Features

More info links:
# How to install SQL Server 2005 Reporting Services on a Windows Vista-based computer
# Installation of SQL Server 2005 in Windows Vista – warning message on IIS feature requirement during System Configuration Check
# Tip for Installing SQL Server 2005 Reporting Service on Vista

Ok, this one is the weirdest error and solution I got. Don’t even ask why in the world do I need to install Office 2003 Web Component add-in while I have Office 2007 installed on my machine. I have no clue, but that’s the only solution I found which works for me. It solves the “OWC11 Setup failed error and the following error message.

MS SQL Server 2005 - Error 1706

ERROR 1706 Setup cannot find the required files. Check your connection to the network, or CD ROM! For other potential solutions to this problem, see c:\Program Files\Microsoft Office\Office11\1033\Setup.chm

You have to download and install “Office 2003 web components” first and install SQL Server 2005 again; which then in my case cleared the error and installed successfully.
# Download: Office 2003 Add-in: Office Web Components – owc11.exe [ 17.6MB ]

After everything is done, remember to install Microsoft SQL Server 2005 Service Pack 2. Pheewww! That’s it!

Source code for .Net Framework Libraries are available for download with the next release of VS 2008 and .Net 3.5 next year.
ScottGu explains more

Have been said, it’s way too advance for me to dig through those source code as I’m still struggling to learn the efficient use of the libraries itself. But hey, it’s all good that you get the source too. Cool!

Licenses.licx and VSS

In our current project, we have to work with WinForms using VS 2005 and VSS as the project source control. There are two solid developers and one developer/Product Manager involved in the coding of this project. Our Product Manager suggests and prefers we use VSS rather than SVN for better source management (check in/out). As for us, developers (me and my bro), we had a great time using SVN in the last project and prefer to use SVN; nevertheless both of us are flexible and agreed to work with VSS after a few discussion. Things are fine when I focus on designing forms and my bro working on code behinds. But the problem arises when we start testing on a few forms, which need both of us to work on design view.

In VS2005 WinForm IDE, it adds or writes to the licenses.licx file whenever you use custom controls/third party controls such as Infragistic in your form. Though I’m not so sure, I observe that the licenses.licx file is not needed if you work entirely with normal winform controls, but with third party controls, it acts as a config file storing the references of the controls.

Once you add a project to VSS DB, the licenses.licx file is always binded since it’s part of the project property. You can check out the code just fine but when you work with the form design, you’re forced to check out the licenses file. If you don’t/can’t check it out, you can’t do anything to the form design. With VSS, it’s really a pain if one developer checked out the licenses file exclusively, others can’t do any design work on any of the forms. To solve the exclusive checkout on licenses file, we tried to exclude the licenses.licx from the project and let it stay in local folder. Unfortunately, the file itself is part of project property and once it’s excluded, it loses the references as well. For that little experiment, I’ve lost two of my form designs and have to start all over; thank god, they were just small forms. With that failed experiment and out of ideas, we searched for the solution on the web. Found out that it was a known issue for VS2005 IDE and the fix would only available with the next release of Visual Studio. The only work around they suggest so far is to use VSS multiple check out mode.

We don’t want to use Multiple check out mode in our VSS DB for:

  1. VSS doesn’t provide individual file multiple check out mode but for the whole DB,
  2. There are a few careful steps to take before checking back in the multiple check out file. (You cannot check in directly. You must get latest on that file to ensure you get different versions from other developers to merge the file then only you can successfully check it back in.)
  3. VSS merge is a real pain and should I would never trust it. Unless ofcos’ you don’t care about losing some of your codes or have a separate backup, go a head and try it out.
  4. There is the need of source control administrator for merging files.
  5. And again, don’t trust VSS Merge and can’t rely on it.

But untill the next VS release, it’s the only possible way so we don’t have a choice but to use that method. Don’t have time to dig up properly either. So gonna stuck with this problem for the whole project. It’s just making my life miserable. *sign*

Readings: MS Feedback | Forum Q&A

I’m wondering – 2.0

I’m wondering…

  • I’m wondering, 2.0 website project does not create project file and .dll file and where all those code-behinds compiled into?
  • I’m wondering, if we are to deploy it, do we only deploy .aspx and .ascx (front-end) files or have to include code-behind files as well?
  • I’m wondering, why .pdb files are also included when you add project references to the website project.
  • I’m wondering, why some referenced .dll creates .xml files as well.
  • I’m wondering, do we need to add those .pdb and .xml along with referenced .dll in the deployment.
  • I’m wondering, the main difference between 2.0 web application project and web site project.

And I’m still wondering…

Flickr Photos


Twitter Status

Goodie Links

Mayvelous Friends

I'm an Author for Global Voices