|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 839293 - Last Review: May 18, 2007 - Revision: 2.4 BUG: IntelliSense feature stops functioning when you switch from Designer view to Code viewWhen you use License controls in Microsoft Visual C# .NET 2003, and you switch to Code view after you make some
changes to a form or a control in Designer view, the Microsoft IntelliSense feature may stop functioning. This article describes how to resolve the
problem by deleting extra blank lines from the licenses.licx file of the project that are incorrectly added by the Microsoft Visual Studio .NET 2003 IDE.
The IntelliSense feature may stop functioning when you make some changes in Designer view, and then you switch to Code view. Color syntax highlighting in the Code view disappears except for the #region directive and comments. You may notice this behavior when you use License controls in your project. When you use the License controls in your project, the licenses.licx file is automatically generated. There may be some blank lines in the licences.licx file that are incorrectly added. These blank lines cause a part of the Language service code to fail, and this behavior causes the CodeSense feature of IntelliSense to disappear. To resolve this problem, follow these steps: - Start Visual Studio .NET 2003.
- On the File menu, click Open Solution, and then locate the solution file where the problem occurs.
- On the File menu, point to Open, and then click File.
- Locate the project folder in the Open File dialog box, and then double-click licenses.licx.
- In the Code window, remove all the blank lines from the end of the type name line in the licenses.licx file by pressing the DELETE key on your keyboard.
- On the File menu, click Save All to save all the files.
- Restart Visual Studio .NET, and then open the project again.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. Steps to reproduce the behavior- Start Visual Studio .NET 2003.
- On the File menu, point to New, and then click Project.
- Under Project Types, click Visual C# Projects, and then click Windows Application under Templates.
- In the Name box, type MyLicensedControlProject, and then click OK.
- On the View menu, click Toolbox.
- Right-click the toolbox, and then click Add/Remove Items.
- In the Customize Toolbox dialog box, click the .NET Framework Components tab.
- Click Browse, and then locate the following path of a sample license control:
InstalledPath\Microsoft Visual Studio .NET 2003\SDK\v1.1\QuickStart\winforms\samples\writingcontrols\licensedcontrol\cs
Note InstalledPath is a placeholder for the path where Microsoft Visual Studio .NET 2003 is installed. - Click LicensedControl.DLL, click Open, and then click OK. The LicensedControl control appears under My User Controls in the toolbox.
- Double-click LicensedControl in the toolbox.
The licensedControl1 licensed control is added to the form, and Visual Studio .NET automatically generates the licenses.licx file under the ProjectPath\MyLicensedControlProject folder.
Note ProjectPath is a placeholder for the path where the project that is named MyLicensedControlProject is created. - On the File menu, point to Open, and then click File.
- In the Open File dialog box, locate the project folder, and then double-click licenses.licx.
- In the Code window, add three or four blank lines to the end of the type name line in the licenses.licx file.
- On the File menu, click Save All to save all the files.
- Restart Visual Studio .NET, and then open the project again.
- Make some changes in Designer view, and then switch to Code view.
You notice the problem that is mentioned in the "Symptoms" section. For more information about Licensing Components and Controls visit the following Microsoft Web site:
APPLIES TO- Microsoft Visual C# .NET 2003 Standard Edition
- Microsoft .NET Framework 1.1
- Microsoft Visual Basic .NET 2003 Standard Edition
| kbide kblicensing kbbug KB839293 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
 |
 |
 |
 |
 |
 |
 |
| |