I have a standard/new Windows 2008 R2 install with SharePoint 2010 and am looking for a SharePoint expectation that occurred sometime during the last week.
So I open windows explorer, then go to the logs directory (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS). In the toolbar I can enter some search text (exception) or i can Ctrl-F which puts my cursor in the same search box. First it searches the filenames, comes back with no results, and then i click File Contents. And it comes back with still no results.
Now I think, maybe there are no errors, so i search for something that I know is in the log (w3wp), still no results.
In previous versions of windows, i could usually fix this by making *.log files read as text.
But apparently (http://technet.microsoft.com/en-us/library/cc725753(WS.10).aspx) *.log files should already be read as text.
Any idea how to make the search, really search log files. I would prefer a solution that did not involve installing any 3rd party software (eg like ULSViewer), but registry/powershell settings are okay.
Windows OOTB txt search sucks without installing something like WIndows Search. ULSViewer is not an install, it's .NEt so just copying it to the machine should suffice.
Related
I have just started experimenting with the Microsoft tools to set up a symbol and source server.
I have successfully indexed my source files using p4index, updated the .pdb files and updated the symbol server.
I have set visual studio to use the my symbol server.
All works fine: when I step debug through my exe as a standalone exe the pdb's are loaded and the correct version of the source code is exported from perforce to temp location and displayed within visual studio.
Whats the problem then? If I try to debug on the machine on which I built my exe then visual studio finds the source code locally. The trouble is that this is a modified file and not the correct version of the source corresponding to when exe was built. VStudio even knows this and pops up a requester saying "the source file is different from when the module was built. Would you like the debugger to use it anyway?"
If I click no then I just get a file dialog to manually locate the source.
Is there a way to get vstudio to fall back to using source server or preferably to use the source server first before looking looking locally?
I'm using visual studio 2012 and perforce
After having encountered the same issue, I finally narrowed it down to the fact that Visual Studio won't run the P4 PRINT command if there is already a file at the place where the pdb/debugger expects to find it.
For example, if the indexed source file was in C:\Toto\Source.cpp, the sole presence of this file when Visual is looking for it will prevent the P4 PRINT.
If i rename it, Visual is correctly printing the file in another unrelated folder (the symbol cache pass).
It's not a fix, it's only a reason, but I'm still investigating.
This behavior is not present in windbg.
In case anyone else finds this thread and has the same problem, the solution in my case was to Enable "Require source files to exactly match the original version" in Options -> Debugging -> General.
It will still prefer the local copies, but only if they are identical, in which case it is the same version it would otherwise grab from the source control server. And if it isn't the right one, it will now display the proper one from the source control server.
I have installed several versions of SQL Server on my machine, but visual source safe insists in opening any .sql file using Sql Server 2008 management studio.
I have changed the default application for files .sql to be opened using SQL Server 2014 management studio but now when I right click any of my scripts, either to view of edit, it comes out with the message "Error executing: DDE connection" as you can see on the picture below.
has anyone got any solution or suggesting for this?
Does this help?
http://social.msdn.microsoft.com/Forums/en-US/fc0c9ac9-e8ba-41a5-9f7e-7486f7d8ea32/vss-no-longer-finds-the-registered-application-for-sql-files?forum=vssourcecontrol
Have you tried setting this extention in VSS
Explorer->Tools->Options->Custom Editor?
or
Could you try the following?
Rename
ft000002 and ft000003 (whichever one you have listed under
OpenWithProgids) keys under HKCR
and
HKML->Software->Classes
Rename .sql record from
HKCU->Software->Microsoft->Windows->CurrentVersion->Explorer->FileExt
and from
HKCR
Add just one association for .sql file using Windows explorer.
Check HKCU->Software->Microsoft->Windows->CurrentVersion->Explorer->FileExt->
OpenWithProgids You should not have ft0000xx files in there now.
Check if VSS is working as expected now if not revert the changes.
I am working with another developer on an applciation. Whenever one of us deletes a file that has been pulled down on the other workstation. TFS doesn't seem to pass down the files as deleted on the next get request.
Short story: I delete file -> Check in -> Team mate does get -> gets build errors due to the files still being on his local disk
Anyone know what we are doing wrong?
We are using local workspaces. We are checking in the delete. Everything we are doing is happening in Visual Studio. Not in a file explorer anywhere.
UPDATE: It has something to do with resharper 8 and TFS not playing well together. When I move a file or safe delete a file with resharper commands TFS doesn't recognize it (the green lock sign is not in solution explorer).
I suggest you to check in your csproj file, he contains all files included in your project, your another developper get latest old csproj, so you find your file
Just installed VS2012 and run across a strange behavior by the one click publish feature.
I'm publishing via FTP and everything works fine except it seems that VS insists on overwriting some files over and over even though nothing's changed.
In VS2010 clicking the "publish" button over and over just runs through the steps and finishes in a few seconds, in VS2012 it takes about two minutes as it keeps copying a 5mb dll and some other stuff too.
P.S the "delete all existing files prior to publish" is off
It's an absolute pain. I've resorted to keeping the solution open in VS2010 alongside the VS2012 and using VS2010 to publish, it's annoying, but it's faster...
Unfortunately there's no option for only changed files in VS 2012. Not sure why they took it out, other than maybe too many people complained that VS wasn't synching properly when their FTP servers were the problem. FTP servers are notorious for not giving back correct file info.
This is real too slow on large amount of files.
My best experience is to remove unused folders not containing assemblies (scripts, css, etc...) this way <ExcludeFoldersFromDeployment>Content;Scripts;Views</ExcludeFoldersFromDeployment>
.
Publish these files straight when you change them . Otherwise publish assemblies from profile .
https://msdn.microsoft.com/en-us/library/ee942158.aspx#can_i_exclude_specific_files_or_folders_from_deployment
I am trying to setup Subsonic ActiveRecord in a web application in Visual Studio 2010 beta 2. In any scenario I get the same error:
Warning 1 The path 'D:\Work\Project\tt\SQLServer.ttinclude' must be either local to this computer or part of your trusted zone.
Everything works just fine on the same machine with VS 2008.
Does anyone else have this problem? Is it supposed to work with VS 2010 and .net 4.0 or I should stick with vs 2008 for the time beeing?
Ok, figured out one solution. I'm sure there could be others out there. I got around this issue by opening VS.NET 2010 and selecting 'Tools | Extenstion Manager' and clicking on the "Online Gallery" option. I selected the Tangible T4 Template Editor and installed the plugin/extension. If you don't see the extension then try sorting by highest rated or perform a search for it.
I closed VS and re-opened the tt file after closing it and voila! No more compile errors ;)
HTH
I had this exact same error "must be either local to this computer or part of your trusted zone", I did get it to work without adding anything to the Trusted Zone, the only thing I did was remove the "language" setting in the SQLServer.ttinclude file, and then edit the files a little (add a space, remove it, save etc.) not sure if this was enough to convince it to build properly the next time I did "Run Custom Tool" on each of the T4 files, but it worked, phew!
I recently hit this on a new Windows 7 (64 bit) install. Once you download the archive, right click on the file and select Unblock before you extract it and all is well. Note that this applies to the VS 2010 release as well.
Add the network share to Trusted sites. First uncheck the Require server verification (https:) for all sites in this zone checkbox.