I've updated an outlook addin with a new version of th manifest file on the microsoft partner center.
It has be deployed on marketplace and appsource with the version updated.
But the update is not delivered to the clients computer on oulook and owa.
Does someone have encounterd the same issue?
How much time does it take to update on clients computer?
Thx
It can take up to 24 hours to roll out the new add-in / manifest file. Here is what MS states for that in MSDN:
It can take up to 24 hours for a new add-in deployment to show up for all users. It can take up to 72 hours for add-in updates, changes from turn on or turn off to reflect for users.
See How long does it take for add-ins to show up for all users? for more information.
Related
I am working on web add-in for Office 365.
This add-in would be used by enterprises.
I have already implemented mail merge for Word desktop version, and now I am trying to implement the same for Word online.
Does Microsoft has provided support for Mail Merge in Word online?
I got some link says that mail merge is not supported in Word online but there were no clue which indicates whether document is latest one.
effectively mail merge objects are not available in the Word JavaScript API, however this is a great ask. Make sure to add/vote for it #uservoice
https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/category/163566-add-in-word
It would be great to be able to ignore files during the Parse.com deploy process. Possibly using a .parseignore or .deployignore file or something.
This feature has been requested many times with little to no resolution. Here are some links from up to a year ago of folks asking for this feature:
https://www.parse.com/questions/ignore-files-on-deploy
https://www.parse.com/questions/ignore-files-on-deploy--2
https://www.parse.com/questions/is-there-a-way-to-explicitly-ignore-files-with-deploy
http://goo.gl/5JyP3z
Parse dev team, please implement this feature or allow the community to do it!
Thanks
Has the OWASP top 10 project not been updated since 2010?
Having had a look at the following site on OWASP I can see that this may be the case: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project
My company is making a big deal out of OWASP compliance, so I just want to be sure that I'm up to date?
Update -- OWASP Top Ten 2017 was released. You can always find the latest version here. https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project
OWASP Top Ten 2013 was released today! You can download here http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202013%20-%20RC1.pdf
AFAIK - there is a 2013 update in progress.
Contact Dave Wichers for more info, or better yet, volunteer on the topten mail list. :)
Yes, the 2010 version of the OWASP Top Ten is the latest version. Before that, the last version was in 2007. If more people volunteered, it would get updated more often, but most of us who work on OWASP projects also hold down full-time day jobs, so progress can be frustratingly slow at times.
Can I have guidence for TFS 2010 for the following areas:
What is the correct use of tfs and the properties that are exposed for each backlog item and task for recording of effort so that we report on progress using the burndown charts and can assess velocity.
It is not obvious to us what is the appropriate workflow for raising questions about functionality against tasks / user stories so that the person who needs to answer them can easily find those tasks / stories that have outstanding questions. And for when the question is answered how the person(s) who need to know the answer are alerted that the answer is there. Maybe tfs is not the right place to do this and we should be manually doing this?
Unless you customized something, the report features you are asking about will light up in the reports if you use the field in the Task work item named Remaining Work - update it regularly - daily if possible.
The database most of the default reports use (Tfs_Analysis) gets updated every 2 hours by default. Some of the reports only show a daily roll-up so depending on what you are looking for you might not see changes until the day after.
As for your 2nd question about how to communicate about missing information in user stories, etc.. you should read the Process Guidance for the template that was used to create your Team Project. I'm guessing you are using the MSF Agile 5.0 template, so do a search for that and "Process Guidance." The Process Guidance is basically the instructions for how to use the TFS work items and reports, etc... It can be found online (on MSDN) or by right-clicking on your team project in Team Explorer and choosing Process Guidance from the context menu. I'm answering this from my phone but can include a link to it later if you find this helpful.
Eric suggests that you read your team's diffs every morning. Can I get TFS to automate this in some way? Ideally I'd like an email with all of the differences in, but I'd settle for a link to each of the commits.
As someone who works for Eric and who has the behaviour of checking the diffs each morning let me explain what I do. I'd like to think that I was one of the people he was thinking about when he wrote the post, but I know for a fact that he didn't know I did the diff checking each morning :-)
In Eclipse I use the Team, Synchronize... functionality to compare my local workspace with the latest on the server. As I do a get latest frequently, this tells me what has happened since I last did this (i.e. what changed while I wasn't looking).
In Visual Studio, I can do a similar thing by right clicking on the root folder of the area that interests me and selecting Compare... and then doing a compare of the Workspace version with the latest version.
Alternatively, you can just do a "History..." on the folder that is of interest and a brief scan down the history view will show you what has been happening and you can go look at what is interesting. It also encourages you to leave good check-in comments, and to encourage your developers to do the same :-)
I used to have email alerts configured for each check-in (Team, Project Alerts...), but I just ended up ignoring them most of the time. I even have a robotic rabbit configured to talk to me when someone does a check-in or runs a build - but this is only useful during the day, not checking what has happened the previous day while I was asleep (I live in a different time-zone to the rest of my colleagues so they do a lot of work while I sleep and vice-versa, making the practise of diff-checking even more useful)
In theory it would be possible to write a program that did generate you a diff each day between the latest version and your workspace version, however I've never bothered myself. This is partly because as I find the most value of the practise comes in exploring the changes that were made each day rather than just reading about them. I also admit that I wasn't aware that anyone else in the world was doing this daily diff routine - I figured I was alone in my code voyerisum, but obviously not!
UPDATE Feb 12, 2009: The following blog post just came to my attention.
http://blogs.msdn.com/abhinaba/archive/2008/07/07/auto-generating-code-review-email-for-tfs.aspx
It talks about (and provides source for) a tool called CRMail that will generate an email from a shelveset that will contain links back to Team System Web Access to show the diffs for each change in the changeset. It would be possible to modify this source to get it to show you diffs between changesets if you wanted to. Then you would just need to hook it up to run either as a nightly scheduled task or on every check-in by subscribing to the check-in event from TFS.
Have you explored setting up a report on the project portal that would show diffs based on date? I haven't done this (and I'm at home now so I can't investigate it), but I know that there is a lot of information you can get out of the portal. Whether you can get code diffs, I don't know.
The other alternative would be automating something with tfsadmin or the power tools. Again, not at work so I can't look at it, though the power tools seem like they may make it possible to do what you want from the docs.
A quick solution would be to configure project alerts to send you one email per changeset.
Filter these into a separate folder in your email client, and review them at your leisure.