I am using aptana studio v 3.4.2.201308081805 on windows 7, I know that v 3.5 is available because I was prompted to update to 3.5 on a different computer.
I have not received the update prompt on my macbook air or on my work computer. Does anyone know how to force aptana to update to v 3.5?
Aptana has removed version 3.5 due to several bugs.
Current stable version is 3.4.2
You can check here Aptana download
Check out the other Stack Overflow question from here. It's also about updating Aptana Studio. Basically, in your case, Aptana may not have the update sites list configured yet. You'll need to import the XML file containing these addresses (many people have had to deal with this, as show in the support thread on Aptana Studio's support site about adding update sites to Aptana. Also, check out this page on the Appcelerator wiki about common issues with updating.
Related
I just installed Visual Studio a few days ago and for some reason I can't create anything but a class.
When I go to create a new User Control the pop up window lets me do everything except for click the "Add" Button to close the window and create the control.
If I double-click the User Control selector to create automatically, it pops up an alert box that says I need to go to the installer to get the .NET Framework target libraries. But when I go to the project's properties I see that I am already targeting .NET Core 3.1 and the only other option I have to target is .NET Core 3.0.... I assume this is because I'm in a .NET Core WPF application but I have no idea why it won't let me create a new control. It won't let me create anything except for a new class.
What is going on here? How can I work around this bug?
I've faced your problem recently. most of the templates were not installed after installation.
something you have to do is Modify your installation.
open Visual Studio Installer and click on Modify then choose the features(.Net core,Asp.net, Desktop Application and etc) in order to re-install them.
keep it in mind that, if installer encounters any problem or missing dll. installation instantly will be completed that should not happen.
keep your eyes close to your installer process and make sure all packages are installed.
a successful installation MUST not have any warning otherwise there are packages not installed.
it's better to install packages one by one NOT totally. I mean if you want the Asp.Net Core feature then try to install it at first. then try to install another feature.
Actually, I was not able to install whole features in a single installation and I don't know why. in short, don't heavy your installation.
If the problem still exists then:
1. Close all open solutions
2. Run InstallCleanup.exe
C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe
3. Remove all existing Visual Studio programs from Control Panel -> program features
4. Restart pc and re-install Visual Studio
5. Make sure you have connected to the network
6. Choose only one feature(Don't select all) to install + Visual Studio Editor
vs bug
Extensions don't work properly in VS 2019 and make it hang. it's may happen because the Extensions have to be updated to be compatible with vs 2019 or it's vs bug.
My visual studio 2017 is not detecting .Net core 2.0 no matter what I do. I am running visual studio 15.4.3 and installed .Net core multiple times with reboots. (no effect)
I tried multiple things like editing the .csproj file and the global.json if it was there (no effect). If I check dotnet --version in my user folder I get "1.0.0-preview2-003121" while if I try it in the "C:\Program Files\dotnet" folder I get "2.0.2"
Even my Environment-variables are not showing any weird path directions to older .Net versions.
Does anyone know a fix which has not been named in these topics?
ASP.NET Core 2 template missing in VS 2017
.NET Core 2.0 missing from my Visual Studio
https://developercommunity.visualstudio.com/content/problem/61785/net-framework-47-not-listed-as-a-target-framework.html
Every tip is appreciated.
Ok after writing the question I realized what the answer was.
As dumb as it sounds I only installed the x64 version and not the x86 so it was never displayed in my SDK folder.
Hopefully this helps another person with the same brain-malfunction =)
I have created a Module(Portal). I am going to publish it. I just don't know which version it can support. The previous versions and future versions. I am just curious above this all specially in case of .DLLs.
Please suggest me.
Development system
1- Visual Studio 2015
2- DotnetNuke 7
DLLs
It will all depend on what version of the DotNetNuke.DLLs you compile your module against.
Typically if you compile against a version, say 07.00.01, the module will run on that version AND any NEWER version of DNN.
There are some cases where there are breaking changes for modules on upgrade of the DNN version, but they are pretty few and far between.
I am trying to publish my Web App in Visual Studio Professional 2013 but getting the following error
I got the same question asked over here but no useful answer.
Can anyone please help
You probably will be using older version, that was having an issue. refer detail [here]
Install the newer web deployment tool, should work.
which .net version are you using.
check web deploy version. if vs has 2 web deploy version, the vs get confuse to take which version. If it has 2 version, just uninstall vs and then instal it along with web deploy. if the Vs has one 1 web deploy version, you uninstall and install the web deploy. It will rectify your problem i hope.
You can refer This link
Check if version 9.0.0.0 of the assembly is installed in GAC. (from the VS2013 developer command prompt) gacutil /l Microsoft.Web.Deployment. Issues like this have occurred in the past where things worked, then after installing an update (or trying to install one) then reports of missing dlls, like nuget, occur.
The usual course of action is to repair the Visual Studio installation.
There is a problem with your publish profile. Delete the pubxml file located bellow Properties folder in your project and then create a new publish profile.
I got the same problem when older project runs into the new .NET Framework, for that you have to do the following.
Right Click on your project name->select Property Pages -> Click Build from the menu-> then select Target Framework .Net framework 4.5 or your current using framework..
"Could not load file or assembly" means the required file (of that mentioned version) is not available in the assembly (nor in the registry). All you gotta to do is to ensure this same is installed properly that would allow you to proceed further. The other things to ensure is the latest framework installed on your system.
Think you have some errors happen when to install or update Visual 2013, so you can reinstall again and this error will be fixed.
I have the unfortunate task of fixing a legacy ASP site that was migrated to Windows Server 2003, and I know nothing about ASP. The main issue appears to be with ASPSmartUpload, of which I have version 2.3 installed. According to http://foradvice.net/smart_upload_faq.htm:
FAQ: does aspSmartUpload work on
Windows 2003 server ?
Yes, last versions of aspSmartUpload
work fine on the Windows 2003 server.
If you upgrade your OS and used an old
version of aspSmartUpload, you have to
download and setup aspSmartUpload
3.2+.
Of course, aspsmart.com doesn't respond and any Google result for "aspsmartupload 3.2" points to the dead link. The latest version I can find anywhere is v3.0, on some dodgy-looking DLL download site.
What is the best way to resolve this, or can anyone provide a working link to version 3.2 of ASPSmartUpload? Thanks!
We searched for quite a while before finding these dlls.
Here is the link for the ASPSMARTUPLOAD.DLL Usage page that tells you how to install it and a link for downloading version 3.3.
From what I understand, windows server 2008 requires version 3.2 or higher, but we couldn't find version 3.2. I believe version 3.3 will work the same.
One other item, we had to get msvbvm50.dll VB Runtimes for this to work on windows server 2008.
Once these files were registered the server restarted we got past this issue.
Fortunately I have a copy of the original v3.3 distribution.
I've shared it here.