The Commercial license grants the Licensee the right to install and use the Product by any developer/on any machine within a company/organization, provided that the total number of developers using the software at a time does not exceed the number of purchased licenses.
The Personal License grants the Licensee, as a Named Authorized User, the right to install and use the Product as long as the Licensee is the only person using it.The product can be installed on different computers, provided that multiple instances of the software will not be used at the same time.
A Personal License is not available to a company, or to an individual who expects reimbursement of the license fee from a company. A Personal License is property of the individual who has purchased it using his/her own funds.
Each PHP Tools for Visual Studio License entitles you to all major and minor updates for a period of one year from the date of purchase. After this period, you may continue to use PHP Tools but are no longer entitled to free updates. In order to continue receiving updates you will need to renew your Maintenance and Support Subscription.
You will receive a renewal notification email when your Maintenance and Support Subscription is about to expire with instructions of how to take advantage of the renewal offer. You can also choose to automatically renew your Maintenance and Support Subscription. The auto-renew option can be enabled or disabled at any time.
For your convenience, PHP Tools for Visual Studio are using Visual Studio Update process. We recommend to turn on automatic check for updates. This way Visual Studio will notify you when an update is available and you can install it directly from Visual Studio. Please make sure your Maintenance Subscription is valid before updating or turning on auto-renewal for your subscription.
To request a refund, please contact us at in...@devsense.com and send us the email address you used for ordering, the order reference number, invoice number and/or other purchase-related information that might be useful.
You can use the PO pre-filled form which will be generated for you. Or you can use your own Purchase Order document. To identify your order, please specify the reference number (the number will be available after the order has been made).
You are a company or a business client registered for VAT in an EU Member State other than Netherlands(our vendor Avangate BV is incorporated in Netherlands), and you have a valid VAT ID. We verify validity of EU VAT IDs using the VAT Information Exchange System
Please only enter capital letters and digits, do not include any blanks or other characters during checkout. If your VAT ID has not been validated, you can finalize the order with VAT and request a deduction afterwards, at p...@2checkout.com
In the US, sales tax is required for transactions in 45 states and it is imposed only on the end-consumers. There are various organizations and individuals that are exempt from sales tax for various reasons. Tax Exemption Certificates (TEC) are the way in which a business, organization or individual attests that it is a tax-exempt entity, or that it is purchasing an item with the intent to use it in a way that has been deemed exempt from tax.
In these cases, 2Checkout (our authorized vendor) can refund the sales tax to the customer's payment account after the transaction is complete. The refund can be requested by the shopper within 90 days of the purchase by emailing a copy of his Tax Exemption Certificate together with the order details to p...@2checkout.com.
Once the initial order is flagged as tax-exempt in our system, all renewals linked to that order will also be tax-exempt as long as the certificate the shopper has provided is still valid at the moment the renewal order is placed.
All licenses provided as part of the Academic License Program are valid for one year.
As long as you're a student, you're welcome to keep taking advantage of the Academic License Program and renew your Academic License for the next year, free.
When you graduate from an educational institution (and thus no longer eligible to renew your Academic License), we would like to offer our congratulations and give you a 25% Graduation discount compliments of DEVSENSE!
The discount should be redeemed within 1 year of the Academic License expiration date. However, should you renew your Academic License, a similar Graduation offer will be available to you the next year around.
Owners of competing products can qualify for 25% discount on new licenses. We do not list the competing products that are eligible, the discount cannot be combined with other discounts and it cannot be applied to an already existing license. Contact us" with a proof of purchase to see if you qualify for the discount.
It would be nice if Devsense supported syntax validation for WordPress functions. I know I can install WordPress locally and it would pick up the functions from there, but then I'd have to maintain the updates, etc... Considering the popularity of WordPress, it would be better if this was built-in. Perhaps Devsense could install a local version of WordPress within its own installation folders and make a hidden reference to that directory. Then each time Devsense is updated, it would include the latest version of WordPress, so it would be completely transparent to the user.
This is a terrible idea. You'd get intellisense of the new version, write code for that and can't run it because you haven't updated. What if a wordpress release breaks BC or has a bug, you now have to upgrade to a broken version just so you can get syntax validation? And why on earth would you waste everyone's storage space by installing wordpress when a majority of users won't be using it.
Also, your so-called "reasoning" makes no sense whatsoever. Clearly, you're just arguing for the sake of being argumentative, not because you have anything valuable to contribute to the discussion. If a new version of WordPress added some new function, that function would then become available to IntelliSense, but obviously nothing is forcing you to use the function. The syntax validation would work just fine on an older version. Sure, some functions eventually become deprecated, but it takes years for a deprecated function to actually be removed from the code base,
Finally, to your assertion that "a majority of users won't be using it", it's actually the other way around. According to WikiPedia, "As of June 2019, WordPress is used by 60.8% of all the websites whose content management system is known. This is 27.5% of the top 10 million websites." But yeah, I guess you're right, no one uses WordPress, LMFAO.
I proposed an idea that would make it more convenient for DevSense to work with the most popular PHP-based content management system on the planet, by far. If you don't use WordPress yourself, then kindly mind your own business.
It does make perfect sense because I've ran into the issue of mismatched framework versions myself before. Minor code changes will break debugging and you'll eventually start to fix deprecations - just to find out that the fix to the deprecation requires a newer version than that of what you're running. Or, obviously, the opposite, where a deprecated function is removed, but you won't/can't update your production system and you subsequently lose syntax validation. I may kindly remind you that 15% still use PHP 5.
I'm not arguing for the sake of being argumentative, I'm simply saying that the negatives outweigh the positives of it. And that doesn't even mention the difficulties of actually implementing this feature into an IDE. What to update - only the core? To beta versions or only to stable ones? To release candidates? What if plugins have a dependency on an older version? What if you WANT to use an older version, now they have to implement the possibility to override the hidden installation. So many questions with so many problems, all to save 30% of users half a minute every few months?
Marc, it's fine to disagree and clearly we do. But there's something to be said for civility and respecting other people's point of view. When you start out a post with, "This is a terrible idea", that's not being respectful.
I don't want to get into a nit picking back-and-forth with you over who's right, particularly since this is subjective. For me, the benefit of having built-in WordPress syntax highlighting vastly outweighs the potential negatives you mentioned. For you, I guess it doesn't. I will say that many other PHP IDEs have implemented this feature, either built-in or as a plugin, so I"m not proposing anything outlandish or unreasonable.
Of course, it should be an optional feature. During the install, there could be a checkbox to also install the latest version of WordPress. Simple, easy, wouldn't affect anything in the IDE and totally up to the user whether he wants to install it or not. I always keep WordPress up-to-date on my websites, because not doing so is a security risk. Therefore, I'd find it convenient to have DevSense automatically update the local WordPress install, each time DevSense is updated.
Hi Brad, I agree. I don't think we'll see eye to eye on this particular feature, but I should have approached the discussion more polite. In the end it's DevSenses decision whether they see this as a feature implementable in a way that there's an easy solution to the problems it could cause.
@Brad @MarcHenderkes php tools may have built-in WordPress function database (just stubs, not the whole code). Only drawback would be, it might not match the version of the WP you actually have on the remote server.
PHP Tools for VS Code is a full development integration for the PHP language. The features are provided respecting conventions, stability, simple use, and performance. Please see the product page for more details on devsense.com.
This package extends VS Code with fast code completion, advanced editor features, code fixes, code lenses, code generators, debugger, built-in development web server, test explorer, tests debugger, and workspace-wide code analysis.
c80f0f1006