I have just update aptana into the 3.6 version but I have lost all connections that I had in my projects. Also, making new projects just won't show the connections row anymore.
I have received an answer in the ticket system of Aptana. In order to see the connections again you have to change the project format from PHP or anything that you have activated into Web. Only that. It doesn't make a lot of sense, but that's how it works now.
To change that you have to go to properties of the project -> project natures and check only Web and make it primary. All the rest of natures must be unchecked.
go to properties of the project -> project natures
check only Web and make it primary
All the rest of natures must be unchecked
Click Ok
go to properties of the project -> project natures
check PHP (Web should still be checked and set to primary)
Click Ok
connections now appear in my project explorer and my php files are still indexed
Had the same problem on Mac OS X 10.9.4 (Maverick).
If you click on down arrow (V) to right of Project Explorer tab and tick projects they should show up.
Hope it works for you!
Patroklo, What kind of projects is the connections missing? I believe in Aptana Studio 3.6.0, the connections are available only to Web Project.
If the primary nature of the project is set to Web, then the connections would show up in the Project/App Explorer. An alternative/workaround in your case might be to set the primary nature of the project to Web (only if it does not have any other side effects).
I tried everything on this page and nothing worked (OS X). The solution that worked was still pretty simple, so hopefully it helps someone else.
Right Click "Connections" and select "Properties".
The connection I had that was not showing local path was set to "Filesystem," but simply checking "Project" fixed everything (it's more logical too... not sure why it selected "Filesystem" this time as it's typically been set to "Project" in the past).
I right-clicked each specific connection, clicked Properties, and then clicked the Test button on the Edit the FTP connection dialog. After it succeeded I was able to click OK and then the connections worked properly.
Related
I AM Using Flex Builder 4 for flex Web application, In which I create one flex Web Application. Now i am trying to run my application on web browser at that time builder shows some error like (Cannot run program "C:\Program Files\Mozilla Firefox\firefox.exe": CreateProcess error=5, Access is denied).
This error shows me from last one day. So will anyone can give me answer that why i got such error. In preferences Default System Web browser is selected. which is Mozilla Firefox.
Thanks
Go to Window -> Preferences -> General -> Web Browser. There you can see the available browsers listed and a radio button for selecting either the internal or external browser. Do check these settings and try to launch again. It may be that the path you have shown, where "firefox.exe" resides has not been updated within the Flash Builder.
Rigth click on the flashbuilder shortcut -> run as administrator
If you can't run as an admin, try checking on the security settings to ensure all users have full access to the Firefox directory & files. This almost has to be security related, unless Firefox is actually a location different from where it's looking.
I just clean and close flash builder project. And then close flash builder and restart my system and then relaunch flash builder then it will works now.
Thanks to all.
VS 2010 Toolbox in ASP.NET application development (design mode or source) is not showing all controls (showing HTML and reporting ones), I can see all by right click (Show all) but they are greyed out or inactive.
I have used devnev.exe in VS Command line to reset, have reinstalled VS, have deleted the four hidden files in C:\Users\Ramzan\AppData\Local\Microsoft\VisualStudio\10.0 with extension .tbd, all in vain.
This thing is driving me mad. I have another machine and everything works fine there.
Any help much appreciated.
Don't know if this applies; but I had all controls in the toolbox disabled; you could see them but they were disabled - This in Visual Studio 2010. I right click on a toolbox item then reset toolbox and then they are enabled. Note that you may lose any custom controls you added.
Probably your project is RUNNING. STOP the project then your toolbar items will become enable.
Right click in toolbox and remove check from "SHOW ALL" (if checked)
This was driving me crazy for a pair of days. In the choose items menu my 3rd party controls (CrystalReportsViewer) were checked. Reset toolbox did nothing to enable them. My solution was changing the target framework from .NET Framework 4 Client Profile to the full version .NET Framework 4, seems the client profile which is a subset of the version optimized for client applications does not support my controls or just using references to other 3rd party .dll librarys. This issue should only be for .NET 3.5 and 4.0, Client Profile is discontinued for .NET 4.5
I had the same problem and fixed it now after 3 days:
reset toolbox (not worked)
close and reopen the solution (not worked)
close and reopen the VS (it worked!)
After a long time googling , and mostly all answers - revolving around
Reset Toolbar
Delete .tbd files from C:\Users(your user)\AppData\Local\Microsoft\VisualStudio\11.0
Using devenv.exe /SafeMode & devenv.exe /ResetSettings.
None of them working out for me, making me more sick.
There is something I did which worked and thought it's worth sharing if it helps someone.
I followed all of the above steps, failing . I did Step 1 & 2 with my project (in VS 2012) open and
Right Click on Toolbox > Choose Items > Pressed Reset > ok.
Then again, Right Click on Toolbox > Add Tab > 'gave it some name' > then again
Reset Toolbox
There was some screen flash/flickering - some loading .
And to my surprise the Grey life ( grey controls ) were now available .
Hope this helps someone like me! :)
This worked for me..
How to completely reset the Toolbox and enable Visual Studio to rebuild it from scratch
Close Visual Studio;
Open the "c:\Users\\AppData\Local\Microsoft\VisualStudio\10.0" (Windows 7) folder and remove all the .TBD files;
Run the "regedit" tool. For this click the "Run" item in the Start menu and type "regedit" without quotation marks;
Find the "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\ToolboxControlsInstaller_AssemblyFoldersExCache" and "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\ToolboxControlsInstallerCache" keys;
Remove everything from these keys leaving them empty;
Run Visual Studio again and wait until it recreates all items in the Toolbox.
If you are working in WPF application and your Xaml is opened with xml, then make sure you right click and view designer, to get your toolbox controls enabled. (Toolbox controls seem to be active(enabled) only in designer mode). At least that was the case with me.
I know this is old but I just encountered the same problem and here is what I did:
Click on Data Flow
Right click anywhere in that window
Select SSIS Toolbox.
Hope this would help someone.
I worked for me doing the following steps:
Reset Toolbox (Right click in Toolbox->Reset Toolbox)
Add a new tab with any name (Right click in Toolbox->Add Tab)
Reset Toolbox (Right click in Toolbox->Reset Toolbox)
What helped me was changing Project type from Windows Application to Class Library - then (after re-build and reopen...) I got all Controls Enabled.
What did it for me on a custom control was to first remove the control from my base project. Then I had to pull up the custom control as a separate solution by itself and recompile it. I had to make sure that that it was compiled as a class library and not as a windows application. I had to make sure that it was compiled with Framework 4 (same as my base solution) and that all sub controls and projects were also using framework 4. Once I got all of those things sorted out I went back to my base project and added the newly compiled control and sure enough it was enabled.
I hope this helps someone.
I tried all the above mentioned still not working for me. I was working on a windows application after that I have started the web application coding on visual studio after that whenever I was opening the Visual studio this problem was occurring. I am using Visual studio 2015. So what I did, I have right-click inside the toolbox panel and selected 'choose option' then under '.Net framework' components tab I have checked all check boxes for which assembly name is 'System.windows.forms' It is working for me now.
Make sure the currently opened solution platform actually supports controls you need.
My problem was, for example, that I tried to add 'SqlConnection' control to .NET 6.0 application.
Once, I created a '.NET Framework Windows Form' project 'SqlConnection' control became available
I've Googled this particular problem, but cannot seem to find a working solution.
Symptoms: After adding a breakpoint in the codebehind for an aspx page in a web application project, the breakpoint displays in the margin as a hollowed out red circle with an exclamation point enclosed in a yellow triangle in the bottom right of the circle. When mousing over the breakpoint, the message "The breakpoint will not currently be hit. No symbols have been loaded for this document."
Note: I'm trying to hit the breakpoints by "attaching to [a] process", namely w3wp.exe, located on a remote computer.
Things I have tried.
Recompiling other projects in the solution.
Checking to make sure that the configuration for each of the projects and the website in the solution is set to "Debug" on "any pc".
Closing the solution and restarting Visual Studio.
Restarting IIS.
Reattaching to the process (w3wp.exe).
I've been trying to hit the breakpoints using Internet Explorer version 9 and Mozilla FireFox version 4. In each case, the breakpoints are never hit.
Any ideas are welcome! Thanks!
Andrew
If you have more than one solution in your project.
Right click on your solution --> Properties
Set as --> Startup Project
Are you deploying your assemblies to the GAC? If not, copy the .pdb file along with the .dll file, placing both in the same bin directory. The debugger should pick up the symbols automatically.
I run into the same problem and guess what? Just do it: At solution explorer, right click on Project -> Package/Publish Settings UNCHECK "Exclude generated debug symbols"...
Maybe it can't solve your specific problem but certainly it will save another people from suffering.
I can't post a screenshot because I don't have 10 of reputation... :(
Like you guys I lost all day searching on google and stackoverflow and the problem was just that. I realized that when I saw the PDB file in the bin folder ready to be published becoming 0 bytes size when I clicked "publish"...
In my case I was trying to debug an ASP.NET Core app hosted in IIS. I noticed that when I published the app (dotnet publish) the generated web.config had this line:
<aspNetCore processPath=".\MyService.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
I had to attach to MyService.exe rather than w3wp.exe to debug the app even though it was running in IIS.
This error produce by many reason, one solution is : its due to different framework version when you try to attach process. For more details, please visit: https://stackoverflow.com/a/13106908/1218422
I realize that this is an old thread, but the one thing that nobody mentioned was to make sure that debugging is enabled in the web.config file.
I had the same problem, fixed it by switching the debugging method. I was clicking F5 with web project set to startup project (and the "Don't open a page. Wait for a request from an external applicaton" selected in project settings).
When I attached VS debugger manually to the w3wp.exe process using the debug menu it worked.
I have this VB ASP.NET Web Service Application project running VS 2005. I'm trying to add references. To do so I click on the "Properties" icon in the Solution Explorer window which presents me with a window to add/update/remove references. I click "Add", I select the reference I want and then "OK". Lo en behold, NOTHING! It simply won't add references (I tried adding several different ones). Specifically I'm trying to add the System.Configuration assembly.
I'm not sure why this is happening, but perhaps another clue to the puzzle is that I also see no "References" folder in the Solution Explorer nor can I view it by clicking the "Show All Files" icon since it's greyed out.
Maybe I'm missing something obvious, I'd be grateful if someone could shed some light on this problem.
P.S: The project is source-controlled using VSS, although it had no effect when I checked out the entired project.
*Progress Updates:
Modified project folder & file permissions, no effect.
Scanned through paths in project source files, they are pointing to correct locations (not that I can see why that would have an effect).
Tried to create a new project and adding the existing project files, this fails horribly.
Stared blankly at the screen for minutes at a time. Forcibly willing it to work has no effect.
After a lot of frustration, cupous amounts of caffiene and nictotine, I managed to find the problem. When you "Get Latest Version" on a folder, be sure to "Set Working Folder" on the root of your VSS database. If you don't do that, the original project code may be duplicated under the main solution file like this:
C:\Projects\MyAwesomeProject
C:\Projects\MyAwesomeProject\MyAwesomeProject
From that you should be able to gather that now you have duplicate code and duplicate configuration files that both gets treated as the main app.config/web.config. Changes made in one is not reflected in the other. When you try to add references it technically adds it to one, but not to the other, also causing VSS not to "show" the references in the solutions property pages.
I second-guessed myself on this one, since I took the project over from a previous developer that didn't set the working folder when he did "Get Latest Version" and check all of the duplicate files created as a result back into VSS. My question was basically "Which one is the right one?".
Deleting "C:\Projects\MyAwesomeProject\MyAwesomeProject\" = Build Successfull.
Happy programming!
I have VS2005 and I am currently trying to debug an ASP.net web application. I want to change some code around in the code behind file, but every time I stop at a break point and try to edit something I get the following error message: "Changes are not allowed when the debugger has been attached to an already running process or the code being debugged is optimized."
I'm pretty sure I have all the "Edit and Continue" options enabled. Any suggestions?
This may seem counter-intuitive, but turn edit and continue off.
There might be another "allow me to edit read-only files" or "allow me to edit even when I am debugging...no really!" setting somewhere, but I don't have 2005 to look at to check.
In 2008, turn off edit and continue and you can edit while it's running (but those changes aren't appplied.)
If you actually want to use edit and continue, you also have to enable it for the project, on the web tab of the project settings.
The application is actually running off of a compiled version of your code. If you modify it it will have to recompile it in order for your changes to work, which means that it will need to swap out the running version for the new compiled version. This is a pretty hard problem - which is why I think Microsoft has made it impossible to do. It's more to protect you from THINKING some changes were made when they really weren't.
For Asp.net it is possible to think of two types of 'edit and continue'.
One is a classic edit and refresh the browser. This works because the browser refresh recompiles everything except precompiled code behind files. This is not referred to as Edit and Continue, though in practice it provides a similar effect. In this mode you cannot change code behind files, because they were precompiled and deployed, but you can change just about anything else.
Another mode allows you to change precompiled code behind files but nothing else ... (this is the mode Chris Bilson mentions which needs to be set on the project properties for ASP.Net). In this case you are using the Edit and Continue feature of the debugger, which knows preciously little about ASP.net. The debugger just sees a loaded .Net assembly and can modify it when stopped in the debugger because there is a project in the solution that claims to know how to build it. In this case you are prevented from modifying things that would otherwise mess up the debugging session. This method however is the only way to change the code while it is running rather than requiring a browser refresh.
You are allowed to make changes to the *.aspx file while it runs, and you can hit refresh on your web instance to see those changes immediately. However, you cannot make changes to the *.cs/*.vb or *.designer.cs/*.designer.vb files while the program runs.
I search for this on Visual Studio 2008 WAP (Web Application Project) and it took me two days to find the solution, so here it is in the hopes it helps somebody else:
There are two locations that have to be checked, one it under tools-options-debugging-Edit And Continue-Enable Edit And Continue, the other is right click project-properties-Web-Enable Edit And Continue
For the record, I had a similar problem with VS 2008 and a different solution resolved the problem for me. Editing code in Visual Studio 2008 in debug mode
Check that you are not in release mode.
In release mode you cannot edit your code while debugging. Just change mode to Debug