Visual Studio :: Edit & Separately Manage CSS Code Rather Than Work In A WYSIWYG Mode?
Jul 31, 2010
A few basic yes/no questions to see if I am expecting the impossible within VWDE:
At one point I thought I was given an option to create an external css file & have all styles automatically stored in the external file. Is there such a setting? ( Right now I have an external css file created & linked to the page, but as I work on the web page in Design view all new styles are created in the web page & I need to use the style manager to move them to the external file. )Can I tell VWDE to generate css for all formatting as I create a new table in the web page in design view? In other words, can I work strictly in web page design view yet have all formatting code - including the table layout - generated into the external css file?If I create style code for a web page table, does that style code need to be manually modified each time I add or remove rows from the table?Is there a VWDE funtion/tool to generate an external css file for an existing web page that contains embedded/inline styles? Right now I find that I need to individually move each style to an external sheet - i.e. Q1.If I were able in some way to create an external css file to handle all formatting for a given web page, would I have to manually create & maintain a second external css file to provide a printer-friendly format?Basically I have found so far that WYSIWYG editting in VWDE is ok up to a point, but support for CSS in Design view is very limited. It seems that if I want to employ CSS, I have to edit & separately manage CSS code rather than work in a WYSIWYG mode.
TI am hoping that even simple yes/no answers to the above will help me determine if VWDE is an exercise in frustration or worthwhile for me.
Visual Studio ( VSTS 2008 ) design mode work good for long time and from about 2 weeks ago it's suddenly stop view any thing in design mode i tried a lot with trying in another projects even in a simple web page but no way it's doesn't view any thing in design mode ... I think to reinstall VS 2008 again but I don't know if is there any outher solution for that ?
migrating my ASP.NET project from IIS 6 to IIS 7.5 I came across an issue with the Managed Pipeline Mode set to 'Integrated'.I have a Global.asax file in my web root to initialize some objects, gather data etc., however I am not able to hit breakpoints in the associated code-behind file (VS 2008). The code is executing very well (as I can tell from Eventlog), but I want to step into all that initializing there and need to have the debugger attached properly.Everything is working as expected in Classic pipeline mode. Since I'd like to benefit from Integrated Mode features in the future I wonder if I have to give up the ability to debug my Application start and error events...
I got a project when after opening in visual studio 2005 in build mode drop down, only debug mode is shown but release mode not shown.Project builds successfully in debug mode is there a way to enable release mode.
Im working on a website project with Visual Studio 2010 from 2 different computers (home & work). In Dreamweaver Im used to FTP to upload/download files to/from a webserver to syncronice my files on the current computer Im working on.What is best option in Visual Studio 2010 to sync project files between home & work computers? I have seen there is a built in FTP, but seems only it can upload files, limited functionality?
can Visual Studio 2008 be All-In-One tool to integrate source code continuously from team members, build, unit test?
Having used Visual Studio Team Edition 2005, unit testing each method within VS itself. I strongly believe that it is feasible to add-on tools. Example ankhsvn tool to use SVN from Visual studio [URL]
In my investigating i have come across number of tools(shown below) to use with Visual Studio 2008 professional
Development tool:- Visual Studio 2008 professional using Subversion as source control tool. Continuous Integration:- Hudson or Cruise control Build tool:- NAnt Testing:- NUnit, Selinium As Visual Studio 2008 can be used for unit testing I think NUnit is out of consideration.
In the same way i would like to have any other tools/add-ons to Visual studio to implement continuous integration, building and unit testing. This process should be automated such a way source code between team members is continuously integrated, built and unit testing is done as configured.
Objective is to use few number of tools as add-on to Visual Studio or achieve most from Visual studio itself (example unit testing). Visual Studio should be all in one tool.
I am aware that Team Foundation Server best suits my requirement, but it is out of scope due to its cost.
I have several places where I have a gridview and dataview set, and when I hit an edit button on the gridview it opens up the dataview. When I hit a cancel button fom the dataview I have this code that returns mew to the gridview:
I am facing a situation where I have to disable GridView field (in EDIT mode ) conditionally.
Here is the situation,GridView has 5 fields "Product Name" "Small" " Medium" "Large" "XLarge"
Here is the problem, application has section where user activate/deactivate sizes (SMALL,MEDIUM,LARGE,XLARGE). Suppose User activates "SMALL" and "LARGE". Now When the GridView is populted normally, I don't have to disable any fields. But when the user clicks "EDIT" on GridView row, I want "MEDIUM" and "XLARGE" fields to appear as disable.
Here is what I know
1) I will have active sizes in SESSION ... in the above case (SMALL and LARGE)
2 I know I have to catch GridView_RowDataBound and then I have to check for the edit mode for the row.
I got a problem regarding CSS in my pages. I managed to apply styles to my page using css and everything looks fine in the Design view. I ran it on IE8 and everything is working fine. Now after I returned to Visual Studio, added some rules to my CSS, and noticing that everything is working fine in the Design view, I ran it again in IE8 and nothing has changed. The rules I added was ignored and it looks the same. I ran it on Firefox and Google Chrome and it's working fine.
But if I ran my project in IE8 through IIS7.5, everything is working fine so it means, the problem is within visual studio 2010.
I am using vs2008 sp1. I am building web site with aspx. I am also using an ajax control. My Site was working normally. I could run it from f5 and it would stop at a debug point. I added an additional aspx page. Then I got a strange error. When I pressed f5 a message box appeared saying that I had not made this version with the debug option. Then from reading an internect post I disabled only my code. That got rid of the message box error but now the debugger does not stop at any break point? Of course this happen when I need to go live with this project in a day.
I was debugging and noticed the following in VS 2008. I had a breakpoint set to see what the values were for the objects used with my parameters in my DAL. I hovered over the object in question and the little window came up with the name of the object(with the blue brick to the left of it), a vertical line, and the objects value to the right of it. This is what I expected to happen.
What I didn't expect is the that I was able to change the value of the object in the little window. I then tried to continue the execution with the new value that I inserted but wasn't able to get the new value to remain. I suspect maybe I didn't do something right.
Is there a way to get the new inserted value(in the little window in break mode) to be used? It seems like there is or I shouldn't have been able to change it..
As far I know this is not supported for asp.net projects. It's quite handy for testing static/shared functions.any info if this will be available in future versions? Or if there are any alternative ways to test your functions in design mode?
So here is the problem, when I build my web application in Win 7 x64 and publish (copy) to 2008 Server R2 (also 64 bit), the application won't run when I navigate to a page that uses a 32 bit dll.
When I boot to the Vista x86 partition and build and publish (copy), same code, minimally modified sln file to redirect to same code location. I've created a new entry usiong Menu > Build > Configuration Manager and created a x86 entry. I thought that was all I needed to do to force VS to build to a 32 bit machine. Am I missing something or do I just need to boot Vista when I want to work on my web site?
This error only happens when I launch an existing application, if I create a new app the error does not appear on that site. However if I try to enter Design mode the Windows Installer opens and hangs. I can still edit the code and even launch the app.
If I click "OK", I get a dialog box that starts a Windows Installer that does not install anything, it justs sits there. If I "cancel" the installer, VWDE dies.
The only thing different on my laptop is that I had Office 2007 Trial installed along side Office 2003 before I installed VWD, I then uninstalled the trial and used the clean-up tool at [URL] to clean up the trial.
I have tried to repair VWDE, I have uninstalled and reinstalled VWDE with no change. Ialso have VB Express running and get no errors when launching it.
In my asp.net application i'm using gridview to which i'm binding data dynamically by writing a select query in code behined file (all column's are autogenerated) now i want to change gridview cell to edit mode from label to textbox or dropdown on clicking of gridview's cell.How can i achive this in code behined file.
I am developing a web site in Visual Studio 2008. I have a project for the web application and several class libraries as references. When I add the references I select the file under bin/debug in the class library folder. When changing the project to release mode the references still point to the .dll in the debug folder. Shouldn't this change automatically. How should I add the references so that debug and release are properly referenced?
We all know that we should only be publishing our ASP.NET Web Applications with release build type, so why do I not get a warning when I trigger the "Publish" command in Visual Studio 2008, for a project configured to build in debug mode? Sure, there might be cases where I need to publish a debug build to a development or test environment, but answering yes in a confirmation dialog would be acceptable in these cases. Is there an option that I have overlooked, forcing Visual Studio to warn me every time I try to publish a debug build? Yes, we could just ban using the "Publish" command and use a more solid build management tool, but this involves a change of process and right not be an option in this particular case.