I've got a macro that updates a copyright header with the most recent edit date.
The problem I have is that the macro currently reads through the entire file rather than just the first 6 lines (which is all it needs).
Is there a way to get the Macro to only read the first "X" lines rather than the entire file?
Private selection As EnvDTE.TextSelection = DTE.ActiveDocument.Selection Private Sub UpdateCopyrightHeader() selection.StartOfDocument() selection.EndOfDocument(True) Dim content As String = selection.Text Dim result = System.Text.RegularExpressions.Regex.Replace(content, regex, "<lastedit>" & FormatDateTime(Date.Now, vbLongDate) & "</lastedit>") selection.Delete() selection.Collapse() Dim ed As EditPoint = selection.TopPoint.CreateEditPoint() ed.Insert(result) End Sub
An example: I have a fairly simple "contact us" kind of HTML form. No controls, just straight HTML, total size of aspx file is 570 lines. There is a Country drop-down list, with roughly 240 lines of "<option value="..">..</option>, one for each country.
Say I need to change the indent of those option lines. I select all ~240 of them, hit TAB and.... wait.
and wait...
and wait...
Finally, VS recovers from whatever trauma I've inflicted upon it, having successfully indented the lines. We actually have other coders getting up with an audible sigh, and going to make coffee in frustration while this sort of thing happens. Just from changing the indent of a bunch of HTML. It also happens when doing a find & replace on that same selection of 240 option lines... huge pause!
Would something be wrong with our setup? Some options (HTML intellisense-related perhaps) which we can adjust so VS doesn't go catatonic when we simply want to change indent? I've resorted to pasting stuff into TextPad, doing the indenting/replacing/whatever, then pasting it back into VS. That can't be an industry standard practice, I can only assume something is off with our installs.
VS's reaction reminds me of Kylie from Fantastic Mr Fox. Select some HTML, hit TAB and...
i have installed visual studio 2010. But when i add a new tool bar like "layout". It all options appears disable (mean i cant select any option). Please how will i enable these options.
I'm not sure what happened, I didn't change any settings. For example, i could type the following:
a{
then hit return, and get
a {
Now though nothing happens. It's not formatting like it used to. where I can set this or switch it back? I checked Tools > Options > CSS but couldn't find anything there that fixed it.
I just can't seem to get C# code to auto-format, despite having gone over all the Formatting options for c# to make sure they are correct. For example, I want brackets to auto-format to a new line, but nothing changes. I want catch keywords to automatically go to a new line, yet they don't. The options are checked in Formatting under C#, so what gives? HTML formatting works, and prop-tab-tab works in c#, but new line formatting and such does not.
I am running Visual Studio 2008. I cannot get the auto format to work on the source code of my aspx page. I have tried it from the edit menu and the ctrl K, D. Nothing works. If I manually fix everything, the next time I open the file the formatting is gone. Here is a sample of what it looks like:
I have a simple class called TaxCalculator when I build solution the building doesn't complete and error list shows this message
" Error 1 Could not write lines to file "objDebugTaxCalculatorComponent.csproj.FileListAbsolute.txt". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. TaxCalculatorComponent"
I am using visual studio 2005 (and team explorer 2005) with tfs 2008. I have installed both Visual Studio 2005 SP1 and VS80sp1-KB932544-X86-ENU.exe.
I perform the following steps:
Select Project->ASP.NET Configuration within Visual Studio 2005. Within Visual Studio 2005, attempt to perform either a check-in or a checkout.
The following happens:
The local server started by Visual Studio starts closing itself. I suspect it is crashing; the systray icons are not properly disposed of. It then reopens itself. It does this over and over again, maybe once every second or two. The TFS progress meter doesn't even budge, it just sits there. Canceling out of the checkout does not work; it says it is cancelling and does nothing.
How can I prevent Visual Studio from naming the classes for new pages that are in folders from being named with the folder name? Does this method not set "right" with anyone else?
When writing inline code in an .aspx file and some lines down closing a statement with <% } %>, Visual Studio tries to be nice but messes it up by rewriting it all. Is there any way of turning this rewriting off, but only for inline code?
and I copy and paste that line in the same page, I usually get the following:
<asp:TextBox runat="server" ID="TextBox1"/>
Obviously, nobody is going to name their controls in that way (if you don't want to name a textbox, simply don't asign an ID to it), and it's not nice having to change the ids of pasted controls. The same happens if I copy a control without an explicit ID, VS simply generates one for me. Is there any way of preventing VS from autogenerating IDs when I copy-paste ASP.NET code?
I'm using Visual Studio 2010 and working on an ASP.NET 4.0 web application. At the moment, a co-worker and I are tweaking CSS, which means constantly changing and saving CSS files and then refreshing the running page in a web browser.Every few saves, the application restarts, causing a considerable delay while we wait for the app to start up, log in again, and return to the page we were working on. In an IIS production environment a CSS file wouldn't go through the ASP.NET ISAPI, but apparently when running with VS2010 and the developent web server this doesn't matter... or something.
I have a question regarding a situation that occurs with GridView, ObjectDataSource in ASP .NET application. The GridView is linked to the ObjectDataSource and both are included within an UpdatePanel letting the GridView to fill in an asynchronous way from a form in the same page so it gets more rows as the user enters the data:
I start the project with Visual Studio 2008, fill the form and it works correctly. Then I stop the execution: rerun again and the data I entered in the previous run is in the GridView. Is like some sort of cache saved the data from the session before. I checked that EnableCaching property is set to false for the ObjectDataSource. If I Rebuild Web Site in Visual Studio (not just Build) then it works corretly leaving the GridView empty. Is this caused just becuase of Visual Studio? Can it be turned off? And will it happen in the final IIS it will run on?
I have a Sitecore/ASP.NET projects that I'm developing. Today at some point I inadvertently hit the "Clean" option in the solution context menu. It took me a while to figure out why my site was hopelessly broken. Turns out Visual Studio went ahead and deleted several required assemblies from the in dir which are not part of my project.How can I prevent this from happening again?The odd thing is that it did NOT delete everything... just a small handful. It left many that are not directly referenced by my project. This makes me wonder exactly what this feature is supposed to do? Is there some sort of file flag I can set? None of the files are set to read-only. If you're interested in details, the following got deleted:
UPDATE: You know what... I guess what I'm really more interested in here is WHY Visual Studio is leaving most of the files and only deleting these specific ones.
I have a multi-tiered application. I would like to publish the class libraries to UI developers to let them add to their web or windows projects to add all the functionality.
I would like to restrict access so only a certain project can be referenced. The reason is so that they do not refer to the data access layer directly and start making calls that would bypass the business logic built into the business tier.
UI->>Business Logic->>Data Access
So in other words, BL and DA are deployed as compiled assemblies. BL references DA. UI will reference BL, but I would like to strictly prevent any other project from referencing DA directly.
