MAMP icon unresponsive, unable to open - wordpress

I have just installed MAMP in Windows 10 alongside my class so that we can begin to work with Wordpress. However, the installed icon, and the app itself within my 'start' search function is unresponsive. I always get this popup: "To run this application, you must install .NET Core." The Popup has MAMP.exe in the corner. I did the recommended download at x64, and got confirmation that it was installed, but I got no result. Any time I try to click on the MAMP icon on my desktop, I get that message. I made sure my Skype was off, I checked if I had multiple Apache installations (I saw none except a years-old one in an archived folder) and I restarted my computer but to no avail. I wonder if there is an issue with the path or the browser -- .NET Core was done with Edge, MAMP was done with Chrome. This is mysterious. If anyone has advice on what to try, much appreciated.

I found the answer! Download x86 version of .NET Core and then install it afterward no matter how old your computer is. I did that and it works perfectly now.

Related

MAMP showing an older version of Wordpress

My macbook shut down unexpected. After starting it again, when going to localhost, I can see an older version of my wordpress website. Looks like the database rolled back. Is there anything I can do ? If not I am loosing most of my work.
I tought it's the cache but I've tried everything that I know to clean the cache and I don't think this is the issue.
I normally use MAMP for MAC, the free version. For some reasons, way back I played with MAMP PRO and it's install on my machine. Now I've just launched MAMP PRO and restarted the servers and BOOOOM! It worked. I can now see my recent changes in my Wordpress website.
I'm still confused why this had happed ? I've searched on google but nothing similar with my problem.

Disable TortoiseSVN project Monitor

I installed TortoiseSVN on my work laptop (win 7 Ent.) and tried to integrate Tortoise with R-Studio. But because of some known issues (see here), I did not take it further and disabled subversioning on R-Studio. Since then, when I start R-Studio client, the Tortoise Project Monitor opens up automatically and takes R-Studio into initialization stage until it crashes and I have to kill R-Studio client.
After playing around for few hours, I learnt that I have to open two instances of R-Studio to be able to run it. So, now, I open R-Studio and let it go into initialization stage and then in the meantime, I open another R-Studio and the 2nd one works fine; then I kill first one. But, it is kind of annoying as the trick does not work sometimes.
I uninstalled R-Studio and reinstalled it again and no change. I am afraid if I uninstall TortoiseSVN and then cannot install it again- as it is an open source and there is no support team to help in case of any trouble.
Wondering if anyone has any idea on how to disable project monitoring at all. I don't really need it at all.
Project Monitor can be disabled in Project Monitor Options.

Qt Creator hangs in Ubuntu Virtualbox

I have a very weird problem. Ive got a an Ubuntu 14.04 running on VirtualBox 4.3.20 r96997. I installed QT Creator a while back and was working with it fine until today. Now when I try to start it, the screen is completely unresponsive, and it endes up freezing (just the QT Creator screen, ubuntu keeps working fine)
I have read in a couple of places that this could be because the welcome mode doesnt play nice with virtualbox 3d hardware acceleration:
Why does Qt Creator 3.0.0 Welcome Mode not work in VM?
http://qt-project.org/forums/viewthread/37412
But im starting ubuntu with the 3d hardware acceleration disabled, and Ive also tried starting it direcly from the terminal by going to the install folder and doing:
./qtcreator -noload Welcome -noload QmlDesigner -noload QmlProfiler
But it also freezes. And the weird thing is that it worked yesterday, and I havent installed any updates or changed the system, it just appears to have stopped working.
Any suggestions?
In the ~/.config/QtProject folder is a lock file (QtCreator.ini.lock). This is the reason why QtCreator freezes. By removing only this file QtCreator will not freeze any more and all the configurations / settings are still there.
Posting my comment as an answer, since OP confirmed it works.
Delete the configuration directory for QtCreator - it's somewhere in ~/.config/

Browser can't find www.dnndev.me to install DotNetNuke

I am working with asp.net and I want to install DotNetnuke (I really need to install it). I have installed it on another computer in the company where I am doign my internship there. But I can't install it on my laptop :#.
First of all I have installed IIS (7.5 didn't worked, after that 8.0) and went through the steps in the 4 part video on how to install dotnetnuke (here is the first part: First Part)
After I did all that, I went to start the isntallation by typing www.dnndev.me on the browser... and I got the error http 500.19 error.... I fixed it by checking some options in the Turn Widnows features on or of (at Programs and Features in Control Panel).
After that I got the error http 500.21 .... I also fixed this by executing aspnet_regiis.exe.
And after executing that .exe file, when I typed www.dnndev.me, all errors where gone... but the Browser couldn't find www.dnndev.me !! I tried it on Chrome, Mozilla and IE... but non of them worken :(..
What's the problem? I removed all the errors, I did all the things in the videos.... why not working on my laptop?
Did you add the binding to IIS for DNNDEV.ME as well as WWW.DNNDEV.ME? The video instructs you to use DNNDEV.ME which is different than WWW.DNNDEV.ME, so you will need to add the binding for WWW if you want to access that.
Right click on the website in IIS, choose Edit Bindings and add the new one there.

visual studio debug error unable to start program no more files

System info: Win 7 x64 SP 1, IE 10, Visual Studio 2010
I've been researching this error all over.
visual studio debug error:
"unable to start program (File path) no more files"
This started with the installation of internet explorer 10 and is happening across all my web projects within Visual Studio 2010.
I've tried all possible solutions (but not VS re-installs) from registry entries (http://forums.asp.net/t/1891930.aspx/1), IE 10 reinstall (fail...won't let me reinstall due to existing version) to switching default launch browser (in Visual Studio, select a different browser such as Chrome to be default browser in "Browse With..." option in project..it works but is pain in the rear) but one thing I just tried which is making me wonder if there is an issue with how IE 10 is launched came from the following experiment:
Basically I did the same process of changing the default browser except that I picked IE 10 x86 version manually in the "Browse With..." option, set it as default and ran project. Voila, it works with no issues.
My next step was to confirm the default IE option in the "Browse With...". I found articles such as (http://lennybacon.com/post/2010/08/22/rehowtochangethedefaultbrowserinvisualstudioprogrammatically) which put me on the path to find out where the settings are for Visual Studios default browser settings.
I checked the browser.xml file and all looked ok including the registry entry pointing to it. I'm unable to check the version of the browser since MS, in it's infinite wisdom decided not to show that info in the Help -> About or anywhere else. so my gut feeling is that the default IE 10 being launched is the x64 bit version.
Does anyone know?
1) how I can confirm the default version of IE 10 launched since afore methods have not worked and
2) why would (I'm assuming) IE 10 x64 launch vs. the defined IE 10 x86 referenced version in the browser.xml file?
Thanks for any and all help.
Dave
UPDATE:
So from doing continual testing, it seems that after I ran the process to change the Default Browser settings in both the registry and the browser.xml file, upon launching the debug process in Visual Studio 2010, it automatically reverted back to the original default broswer settings which would launch the x64 version of IE 10. So in my case, it seems that the issue (error above) lies in the fact that debugging in Visual Studio 2010 using x64 browsers would cause the error. With no recourse, I ended up removing IE 10 from Windows Features and going through a painful process of getting IE 9 back on my system, I now can effectively debug using IE (x86).
It seems that MS is not pursuing any fixes for this issue of the default browser in VS 2010 from what I've read. There are in browser tools I've seen to do the default browser setting changes but don't want to bother with it/don't trust it will work.
Hopfully this helps others dealing with the same pain I have endured...
Thanks
Dave
When I ran into this problem (using IE 11) I noticed that iexplore was open about a hundred times in the task manager. After killing them all I was able to open my project just fine.
Since then, I have made a .bat file with this code: taskkill /F /IM iexplore.exe /T
so now I just run the .bat when I get that error. (alternatively you could run that code from the cmd)
James Butler's response is good for killing all the open IE processes. Which seems to be the issue here. The best solution I have been using is to just set, "Don't open a page. Wait for a request from an external application." then I just refresh the URL (if already open in browser) each time I rerun the debugger.
Access in Project properties under the, "Web" option. Then change setting there.
Check the following registry key
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\TabProcGrowth
Make sure that the value is Minimum
I started getting this error today after restarting from a Windows Update. I'm on Windows 8.1 desktop using VS.NET 2013. To fix I had to add another browser choice in VS debug that was pointing to the x86 version of IE11, and set that as the default. Although the post alludes to the x64 vs x86 browsers being the issue, this seems like an easier solution than the original poster's process of uninstalling and reinstalling browsers.
This blog explains how to set the default browser for debugging to IE x86: http://weblogs.asp.net/gurusarkar/visual-studio-web-developer-express-starting-two-instances-of-internet-explorer-and-throwing-an-error
Have you tried this: "...try selecting the project node in Solution Explorer and choose Set as StartUp Project". Just worked for me.
https://social.msdn.microsoft.com/Forums/en-US/efd93f22-1f1f-4fb1-8ff3-e29104780572/unable-to-start-program-there-are-no-more-files?forum=lightswitchgeneral
I think this is caused by a more general issue of low available system memory. In my case, Performance Monitor showed I was using 82% of my available memory when I was receiving the error. Looking at the processes, the culprit for me was lots of Chrome processes. I shut down Chrome, which freed up about 2 GB of memory, and then I was able to run the debugger successfully. Shutting down lots of IE processes would achieve the same thing of freeing up lots of memory. So I think the solution is just to free up system memory by shutting down whatever processes you don't need open.
This is what is working for me with windows 11 and edge:
Project Start Options - Don't open a page. Wait for a request from an
external application.
Start - Local IIS (Microsoft Edge)/Script
debugging disabled
Create a shortcut to launch the application like
this: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
http://localhost/MyApplication/

Resources