{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 淡お忘 的问题《ASP.NET Server Control - How to add AssemblyInfo f》','https://www.manongdao.com/q-623899.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I've noticed on a few tutorials online that when a new ASP.NET Server Control is added, it automatically includes Properties folder (containing AssemblyInfo.cs) and a References folder.
This works fine for me when creating a C# Server Control, but in VB.NET I just get a template .vb file and a Project file.
Why is this and how can I get an AssemblyInfo.vb file?
AssemblyInfo.vb file is created for every project. By default it is not displayed in the Solution/Project Explorer.
To view this file and others in Visual Studio click Project >> Show All Files menu items.